[ath9k-devel] WMP300N - Authen but no Assoc

[Paul Koan <gmane@airbred.com>]

Jouni Malinen wrote:
> On Wed, 2009-01-14 at 05:24 -0800, Paul Koan wrote:
>   
>> I am using a Linksys WMP300N  (AR5146 + AR2133, 168c:0023) with a WRT610N access point.  The access point is set to N only, using WPA2-Personal.
>>     
>
> It would be interesting to understand how exactly the AP is enforcing
> the "N only" part taken into account the error you are seeing..
>
>   
This isn't clear, but I'll try "mixed" mode to see if there is a
difference - my intent to was to narrow the focus.

>> With a stock 2.6.27-r7 kernel ath9k driver, I am able to connect to the AP using wpa_supplicant, using the config below.  The speed is not particularly good, perhaps 2-4Mbps.
>>     
>
> Does this association work every time (i.e., you do not see that "AP
> denied association (code=18)" message)?
>   
I did a scan through log/messages, and I don't see the error when using
the stock kernel.
>   
>> I have tried a variety of combinations of wireless-testing and wireless-compat since, and each of them seem to give the same problem, so I think I may be missing something in my config.  Hopefully someone here can help.
>>
>> My latest attempt was with the above kernel, and with compat 2009-01-12.
>>     
>> The card fails to associate - I get (repeated endlessly) in dmesg:
>>     
>
> Does this happen every time (i.e., you can never associate with this
> kernel/driver version)?
>
>   
Thats right - at least, I have never seen any evidence of an association.

>> wlan1: AP denied association (code=18)
>>     
>
> That indicates that the AP is rejecting the attempted association and
> the given reason (code=18) indicates that the STA did not support all
> rates in the basic rate set. This should not really happen, so I'm not
> sure what exactly the AP is trying to do here..
>
> If you have possibility of using a wireless sniffer to capture the
> management frames exchanged between the AP and the client using ath9k,
> it would be very helpful to see what is included in the association
> request and response frames. It would also be useful to see what the AP
> is advertising in its Beacon/Probe Response frames. Could you please at
> least send "iwlist wlan0 scan" output for the AP (replace "wlan0" with
> suitable interface name, if needed) from the client?
>
>   
Yeah - if the "N-Only" enforcement is a fudge, then perhaps this is
contributing to the problem.  Here is the iwlist:

          Cell 02 - Address:
00:22:6B:68:B0:5C                              
                   
ESSID:"essid2ghz"                                          
                   
Mode:Master                                             
                   
Channel:6                                               
                    Frequency:2.437 GHz (Channel
6)                         
                    Quality=85/100  Signal level:-40 dBm  Noise
level=-95 dBm
                    Encryption
key:on                                       
                    IE: WPA Version
1                                       
                        Group Cipher :
TKIP                                 
                        Pairwise Ciphers (2) : CCMP
TKIP                    
                        Authentication Suites (1) :
PSK                     
                    IE: IEEE 802.11i/WPA2 Version
1                         
                        Group Cipher :
TKIP                                 
                        Pairwise Ciphers (2) : CCMP
TKIP                    
                        Authentication Suites (1) :
PSK                     
                    IE: Unknown:
2D1A0C181AFFFF000000000000000000000000000000000000000000
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18
Mb/s                
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9
Mb/s                 
                              12 Mb/s; 48
Mb/s                                          
                   
Extra:tsf=000001ee34a1f8c5                                          
                    Extra: Last beacon: 270ms ago

It certainly doesn't list anything quicker than G speeds.

>> Here is the wpa_supplicant.conf:
>>
>> network={
>>   ssid="essid5ghz"
>>   psk="secret"
>>   proto=RSN
>>   key_mgmt=WPA-PSK
>>   pairwise=TKIP CCMP
>>     
>
> If you are using 802.11n only configuration, I would highly recommend
> removing TKIP from the list of allowed pairwise ciphers. It is not
> allowed when 802.11n is used (TKIP may end up being used for
> group/broadcast frames, but not for pairwise) and can cause various
> problems that may be otherwise difficult to identify.
>   

Thanks - I'll turn it off...

> - Jouni
>
>
>   

-- 
*email: paul at airbred.com | msn: paul at airbred.com | gtalk:
paul at g.airbred.com | skype: paulkoan | y!: paulxkoan | blog:
http://www.servwise.com/blog-paul*
------------------------------------------------------------------------
*ServWise Advanced Hosting www.servwise.com <http://www.servwise.com>
*Standard and Reseller web hosting on Windows and Linux* *