#9936 NORM Not Tri: First WPA2 association (TKIP/AES) always fails, retries succeed
Zarro Boogs per Child
bugtracker at laptop.org
Fri Jan 8 07:42:04 EST 2010
#9936: First WPA2 association (TKIP/AES) always fails, retries succeed
------------------------------------+---------------------------------------
Reporter: cabalde | Owner: martin.langhoff
Type: defect | Status: new
Priority: normal | Milestone: Not Triaged
Component: not assigned | Version: 1.0 Software Build 802
Resolution: | Keywords:
Next_action: never set | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
------------------------------------+---------------------------------------
Comment(by cabalde):
We did not find problems with the version 767.
We probed with diferent AP (mikrotik, asus, belair and wavion), all of
them had the same behaviour.
We worked with a mikrotik RB433 (wireless mini-PCI card R52) for creating
the logs.
Replying to [comment:3 martin.langhoff]:
> Thanks for updating the logs. I have reviewed / correlated the tkip log
with messages, the "action" is all at 9:30:30 (11:30:30 on the
wpa_supplicant log).
>
> It looks like
>
> * supplicant reports EAP success _and_ failure:
> {{
> Wed Dec 30 11:30:30 2009: EAPOL: External notification - EAP success=0
> Wed Dec 30 11:30:30 2009: EAPOL: External notification - EAP fail=0
> }}
>
> * then wpa_supplicant completes the association, sends an "association
successful" msg to NM, and then immediately disconnects (and "blacklists"
the BSSID) -- just as NM is firing up dhclient
>
> Next steps:
>
> Cecilia - the 'messages' file doesn't seem to cover the AES run, and I
would like to see the success logs too, against the same AP. Can you do a
new run of associations - capturing messages and wpa_supplicant log for
success and failure of TKIP and AES? We'll end up with 8 files total I
guess.
>
> If that is inconclusive, I will try to prepare some patched
wpa_supplicants for you to try; in preparation for that, could you confirm
if:
>
> - Does the 8.2.0 build show this bug? http://wiki.laptop.org/go/8.2.0
-- It will be affected by the random failure I fixed in NM, but I suspect
it may not be affected by the bug we are discussing here: "first WPA2
attempt always fails".
>
> - Does the latest "F11-for-XO-1" build show this bug?
>
> - What make/model of AP is this tested with? What chipset does it use?
Have you tested different APs/chipsets? (For example - WPA2/TKIP works
correctly for me with an Apple AirportExpress.)
--
Ticket URL: <http://dev.laptop.org/ticket/9936#comment:7>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list