Strange problem with ath9k and ASUS N66U AP.

Jouni Malinen j
Tue Apr 24 23:08:53 PDT 2012

On Tue, Apr 24, 2012 at 05:26:07PM -0700, Ben Greear wrote:
> On 04/24/2012 03:50 PM, Ben Greear wrote:
> > I am trying some ath9k virtual clients against an ASUS N66U.

> > Here is part of the N66U wifi log showing that it
> > thinks sta11 is not authorized:
> >
> > 00:95:95:00:00:0C  associated
> > 00:95:95:00:00:0D  associated authorized

> Here's a better log.  Makes me think supplicant might be at fault???

Looks more like an AP bug to me..

> sta8 failed, sta9 works fine.  The difference appears to be the extra
> RX EAPOL packet that sta8 receives...

> 1335313181.999422: sta8: WPA: RX message 3 of 4-Way Handshake from c8:60:00:e8:88:b0 (ver=2)
> 1335313181.999465: sta8: WPA: Sending EAPOL-Key 4/4

> 1335313182.063695: sta8: WPA: RX message 3 of 4-Way Handshake from c8:60:00:e8:88:b0 (ver=2)
> 1335313182.063745: sta8: WPA: Sending EAPOL-Key 4/4

Either the AP did not receive the first EAPOL-Key 4/4 or processed it
only after retransmitting 3/4. Supplicant side will need to to reply to
retransmitted 3/4 to complete the 4-way handshake. If the AP received
either of these 4/4 messages, it should be fine with the result. If it
didn't receive either, it should disconnect the station. It does not
look like either of those happened.

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list