[ath9k-devel] WMP300N - Authen but no Assoc

[Paul Koan <gmane@airbred.com>]

Paul Koan wrote:
> 
> Jouni Malinen wrote:
>> On Wed, 2009-01-14 at 05:24 -0800, Paul Koan wrote:
>>
>> 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.
>

Mixed mode on the AP didn't produce a different outcome - though the error has
changed, see below.
 
>>> 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.

 Yes confirmed, the denied message does not occur with the stock kernel driver.

>>   
>>>     
>>> 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)

Instead of denied, I am now getting deauthenticated

wlan1: direct probe to AP 00:22:6b:68:b0:5c try 1
wlan1 direct probe responded
wlan1: authenticate with AP 00:22:6b:68:b0:5c
wlan1: authenticated
wlan1: associate with AP 00:22:6b:68:b0:5c
wlan1: RX ReassocResp from 00:22:6b:68:b0:5c (capab=0x411 status=0 aid=1)
wlan1: associated
wlan1: deauthenticated (Reason: 15)
wlan1: direct probe to AP 00:22:6b:68:b0:5c try 1

Do you know what reason 15 is?  Is there a guide somewhere?
>>
>> 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?
>>

Here is the updated iwlist:

          Cell 08 - Address: 00:22:6B:68:B0:5C                                                             
                    ESSID:"essid2"                                                                         
                    Mode:Master                                                                            
                    Channel:6                                                                              
                    Frequency:2.437 GHz (Channel 6)                                                        
                    Quality=93/100  Signal level:-47 dBm                                                   
                    Encryption key:on                                                                      
                    IE: Unknown: 000668756D697432                                                          
                    IE: Unknown: 010882848B962430486C                                                      
                    IE: Unknown: 030106                                                                    
                    IE: Unknown: 2A0100                                                                    
                    IE: Unknown: 2F0100                                                                    
                    IE: IEEE 802.11i/WPA2 Version 1                                                        
                        Group Cipher : TKIP                                                                
                        Pairwise Ciphers (2) : CCMP TKIP                                                   
                        Authentication Suites (1) : PSK                                                    
                    IE: Unknown: 32040C121860                                                              
                    IE: Unknown: 2D1A0C181AFFFF0000000000000000000000000000000
00000000000                  
                    IE: Unknown: 3D1606081100000000000000000000000000000000000000                          
                    IE: Unknown: DD930050F204104A00011010440001021041000100103
B0001031047001020B08000A00020B080
00A04000000000102100244C696E6B7379732C2041204469766973696F6E206F6620436973636F
2053797374656D73102300075752543631304E1024000876312E30302E30301042000234321054
000800060050F2040001101100075752543631304E100800020088103C000103                                                                                                 
                    IE: Unknown: DD090010180200F0050000                                                    
                    IE: WPA Version 1                                                                      
                        Group Cipher : TKIP                                                                
                        Pairwise Ciphers (2) : CCMP TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E006
2322F00
                    IE: Unknown: DD1E00904C330C181AFFFF00000000000000000000000
0000000000000000000
                    IE: Unknown: DD1A00904C34060811000000000000000000000000000
00000000000
                    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=0000000c3f4fc698
                    Extra: Last beacon: 260ms ago

>> 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.
>>   
> 

Done.

> 
>> - Jouni

Thanks - any pointers?

Paul