* [ath9k-devel] WMP300N - Authen but no Assoc
@ 2009-01-14 13:24 Paul Koan
2009-01-14 13:57 ` Jouni Malinen
0 siblings, 1 reply; 5+ messages in thread
From: Paul Koan @ 2009-01-14 13:24 UTC (permalink / raw)
To: ath9k-devel
Hello,
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.
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.
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:
======================
wlan1: AP denied association (code=18)
wlan1: association with AP 00:22:6b:68:b0:5c timed out
wlan1: authenticate with AP 00:22:6b:68:b0:5c
wlan1: authenticate with AP 00:22:6b:68:b0:5c
wlan1: authenticated
wlan1: associate with AP 00:22:6b:68:b0:5c
wlan1: RX AssocResp from 00:22:6b:68:b0:5c (capab=0x411 status=18 aid=0)
wlan1: AP denied association (code=18)
=====================
This is on a gentoo server, and when I init.d the interface, which runs wpa_supp, I get:
* Starting wlan1
* Starting wpa_supplicant on wlan1 ...
ioctl[SIOCSIWMODE]: Device or resource busy
Could not configure driver to use managed mode
ioctl[SIOCSIWAUTH]: Operation not supported [ ok ]
th param 4 value 0x0 -
* Starting wpa_cli on wlan1 ... [ok ]
* Backgrounding ...
======================
Here is the wpa_supplicant.conf:
===================
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1
network={
ssid="essid5ghz"
psk="secret"
proto=RSN
key_mgmt=WPA-PSK
pairwise=TKIP CCMP
group=TKIP CCMP
priority=20
}
network={
ssid="essid2ghz"
psk="secret"
proto=RSN
key_mgmt=WPA-PSK
pairwise=TKIP CCMP
group=TKIP CCMP
priority=30
}
===============================
I'd like to get this working better than it actually is of course, but given that I am using pretty standard gear, I'd be happy to do any testing that might help contribute to the driver.
Cheers,
Paul
^ permalink raw reply [flat|nested] 5+ messages in thread* [ath9k-devel] WMP300N - Authen but no Assoc
2009-01-14 13:24 [ath9k-devel] WMP300N - Authen but no Assoc Paul Koan
@ 2009-01-14 13:57 ` Jouni Malinen
2009-01-14 14:12 ` Paul Koan
0 siblings, 1 reply; 5+ messages in thread
From: Jouni Malinen @ 2009-01-14 13:57 UTC (permalink / raw)
To: ath9k-devel
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..
> 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 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)?
> 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?
> 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.
- Jouni
^ permalink raw reply [flat|nested] 5+ messages in thread* [ath9k-devel] WMP300N - Authen but no Assoc
2009-01-14 13:57 ` Jouni Malinen
@ 2009-01-14 14:12 ` Paul Koan
2009-01-15 5:23 ` Paul Koan
0 siblings, 1 reply; 5+ messages in thread
From: Paul Koan @ 2009-01-14 14:12 UTC (permalink / raw)
To: ath9k-devel
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* *
^ permalink raw reply [flat|nested] 5+ messages in thread* [ath9k-devel] WMP300N - Authen but no Assoc
2009-01-14 14:12 ` Paul Koan
@ 2009-01-15 5:23 ` Paul Koan
2009-01-15 6:27 ` Paul Koan
0 siblings, 1 reply; 5+ messages in thread
From: Paul Koan @ 2009-01-15 5:23 UTC (permalink / raw)
To: ath9k-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread* [ath9k-devel] WMP300N - Authen but no Assoc
2009-01-15 5:23 ` Paul Koan
@ 2009-01-15 6:27 ` Paul Koan
0 siblings, 0 replies; 5+ messages in thread
From: Paul Koan @ 2009-01-15 6:27 UTC (permalink / raw)
To: ath9k-devel
Paul Koan wrote:
> Paul Koan wrote:
>>
>> Jouni Malinen wrote:
>>> On Wed, 2009-01-14 at 05:24 -0800, Paul Koan wrote:
> 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.
>>>
Changing the mode to mixed allowed the router to select between WEP, WPA and WPA2
I received the same deauth with WPA, but wep associates ok with the compat-wireless-20081221 driver.
>
> Done.
>
>>
>>> - Jouni
>
> Thanks - any pointers?
>
> Paul
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-01-15 6:27 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-14 13:24 [ath9k-devel] WMP300N - Authen but no Assoc Paul Koan
2009-01-14 13:57 ` Jouni Malinen
2009-01-14 14:12 ` Paul Koan
2009-01-15 5:23 ` Paul Koan
2009-01-15 6:27 ` Paul Koan
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.