Am Dienstag, den 20.05.2008, 12:53 -0600 schrieb Dann Church: > I am running Fedora 9 with NetworkManager-0.7.0-0.9.3.svn3623 on a > laptop with a Intel 4965AGN wireless card. > > With this setup, I can connect to networks on the 2.4GHz frequencies > just fine. However, I have (both at work and at home) a wireless router > that are dual-band and have unique SSIDs for the 5GHz bands, and cannot > connect with NetworkManager to the AP using these frequencies. > > >From iwlist scan, I see: > > wlan0 Scan completed : > Cell 01 - Address: <my AP mac here> > ESSID:"dd-wrt-5G" > Mode:Master > Frequency:5.18 GHz (Channel 36) > Channel:36 > Quality=49/100 Signal level=-79 dBm Noise > level=-127 dBm > Encryption key:on > IE: IEEE 802.11i/WPA2 Version 1 > Group Cipher : CCMP > Pairwise Ciphers (1) : CCMP > Authentication Suites (1) : PSK > Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s > 36 Mb/s; 48 Mb/s; 54 Mb/s > Extra:tsf=foo > > which clearly shows the frequency/channel info, but in nm-tool: > > - Device: wlan0 > ---------------------------------------------------------------- > Type: 802.11 Wireless > Driver: iwl4965 > State: disconnected > HW Address: <my wireless card MAC> > > Capabilities: > Supported: yes > > Wireless Settings > WEP Encryption: yes > WPA Encryption: yes > WPA2 Encryption: yes > > Wireless Access Points > dd-wrt-5G: Infra, <my AP mac here>, Freq 0 MHz, Rate 0 Mb/s, > Strength 55 WPA2 > > In /var/log/wpa_supplicant.log, I just see: > > Trying to associate with <my AP mac here> (SSID='dd-wrt-5G' freq=0 MHz) > Authentication with <my AP mac here> timed out. > > In /var/log/messages, I have: > > May 20 12:46:37 superfly NetworkManager: <info> Activation (wlan0) > Stage 1 of 5 (Device Prepare) scheduled... > May 20 12:46:37 superfly NetworkManager: <info> Activation (wlan0) > Stage 1 of 5 (Device Prepare) started... > May 20 12:46:37 superfly NetworkManager: <info> (wlan0): device state > change: 6 -> 4 > May 20 12:46:37 superfly NetworkManager: <info> Activation (wlan0) > Stage 2 of 5 (Device Configure) scheduled... > May 20 12:46:37 superfly NetworkManager: <info> Activation (wlan0) > Stage 1 of 5 (Device Prepare) complete. > May 20 12:46:37 superfly NetworkManager: <info> Activation (wlan0) > Stage 2 of 5 (Device Configure) starting... > May 20 12:46:37 superfly NetworkManager: <info> (wlan0): device state > change: 4 -> 5 > May 20 12:46:37 superfly NetworkManager: <info> Activation > (wlan0/wireless): connection 'dd-wrt-5G' has security, and secrets > exist. No new secrets needed. > May 20 12:46:37 superfly NetworkManager: <info> Config: added 'ssid' > value 'dd-wrt-5G' > May 20 12:46:37 superfly NetworkManager: <info> Config: added > 'scan_ssid' value '1' > May 20 12:46:37 superfly NetworkManager: <info> Config: added > 'key_mgmt' value 'WPA-PSK' > May 20 12:46:37 superfly NetworkManager: <info> Config: added 'psk' > value '<omitted>' > May 20 12:46:37 superfly NetworkManager: <info> Config: added 'proto' > value 'WPA RSN' > May 20 12:46:37 superfly NetworkManager: <info> Config: added > 'pairwise' value 'TKIP CCMP' > May 20 12:46:37 superfly NetworkManager: <info> Config: added 'group' > value 'WEP40 WEP104 TKIP CCMP' > May 20 12:46:37 superfly NetworkManager: <info> Activation (wlan0) > Stage 2 of 5 (Device Configure) complete. > May 20 12:46:37 superfly NetworkManager: <info> Config: set interface > ap_scan to 1 > May 20 12:46:37 superfly NetworkManager: <info> (wlan0): supplicant > connection state change: 0 -> 2 > May 20 12:46:39 superfly NetworkManager: <info> (wlan0): supplicant > connection state change: 2 -> 3 > May 20 12:46:54 superfly NetworkManager: <info> (wlan0): supplicant > connection state change: 3 -> 0 > May 20 12:46:54 superfly NetworkManager: <info> (wlan0): supplicant > connection state change: 0 -> 2 > May 20 12:47:02 superfly NetworkManager: <info> Activation > (wlan0/wireless): association took too long. > > > Any debugging to do to see why we're not seeing the frequency? Also, is > this the reason we're not getting a successful association with the AP? > > Hi, I am havin the very same problem with some 2.4Ghz APs here at university. Without any prove I would rather blame the driver than NM as it works[TM] at home. (so it could be a good idea to file a fedora bug) regards christoph
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil