Re: Detecting 5GHz wireless networks

[Dann Church <dann church cassatt com>]

Thanks Dan.  This looks to be the case as when I try the scan under
wpa_cli I get the same (0 freq) result on my 2.6.25 kernel.  I'll post
my info to that thread and see if the fix can be backported when it is
done.

--Dann

On Thu, 2008-05-22 at 13:13 -0400, Dan Williams wrote:
> On Tue, 2008-05-20 at 12:53 -0600, Dann Church wrote:
> > 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.
> 
> This thread on linux-wireless might have something to do with it:
> 
> iwl4965 - wpa_supplicant can't see 5Ghz frequencies - 2.6.26-rc1 kernel
> 
> The bug isn't just on 2.6.26 AFAIK.
> 
> Dan
> 
> > >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?
> > 
> > 
-- 
Dann Church:  (w) 719.388.4678
              (m) 303.888.1263
              (im) dannchurch (yahoo/aim)

You can't judge a book by the way it wears its hair.