#8799 HIGH 8.2.1: WPA association issue when attempted from GUI: XO do not respond to first EAPOL frame

[Zarro Boogs per Child]

#8799: WPA association issue when attempted from GUI: XO do not respond to first
EAPOL frame
-----------------------------------+----------------------------------------
           Reporter:  carrano      |       Owner:  jcardona     
               Type:  defect       |      Status:  new          
           Priority:  high         |   Milestone:  8.2.1        
          Component:  wireless     |     Version:  not specified
         Resolution:               |    Keywords:               
        Next_action:  communicate  |    Verified:  0            
Deployment_affected:               |   Blockedby:               
           Blocking:               |  
-----------------------------------+----------------------------------------

Comment(by jcardona):

 The wpa_supplicant logs provide good information about what's going on.
 Let me document here the steps that we had to follow to get proper logs,
 as it's not straightforward.

 wpa_supplicant is launched by NetworkManager, with hard coded parameters¹.
 In order to get logs, you must write a wrapper to set the right arguments:

 {{{
 # mv /usr/sbin/wpa_supplicant /usr/sbin/wpa_supplicant.real
 }}}

 Then {{{create /usr/sbin/wpa_supplicant}}} as:
 {{{
 #! /bin/bash

 exec /usr/sbin/wpa_supplicant.real -g /var/run/wpa_supplicant-global -d -t
 \
         -f /var/log/wpa_supplicant.log
 }}}

 and make it executable

 {{{
 chmod a+x /usr/sbin/wpa_supplicant
 }}}

 Once you've done this, you should be able to monitor wpa_supplicant state
 transitions:
 {{{
 # tail -f /var/log/wpa_supplicant.log | grep State
 1226112022.535501: State: DISCONNECTED -> ASSOCIATED
 1226112022.541054: State: ASSOCIATED -> 4WAY_HANDSHAKE
 1226112022.560642: State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
 1226112022.562814: State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
 1226112022.575862: State: GROUP_HANDSHAKE -> GROUP_HANDSHAKE
 1226112022.579278: State: GROUP_HANDSHAKE -> COMPLETED    # <-- this is
 good!
 1226112028.712669: State: COMPLETED -> DISCONNECTED
 ...
 1226112151.722583: State: DISCONNECTED -> SCANNING
 1226112151.736786: State: SCANNING -> ASSOCIATING
 1226112152.293060: State: ASSOCIATING -> 4WAY_HANDSHAKE
 1226112152.309323: State: 4WAY_HANDSHAKE -> ASSOCIATED  # <-- this is bad!
 1226112153.339174: State: ASSOCIATED -> DISCONNECTED
 }}}

 The second part of the log shows an instance where wpa_supplicant is
 notified that an association request succeeded '''while the 4WAY_HANDSHAKE
 was already under way'''.

 We still do not have a solution for this.

 --

 [1] Apparently creating a file called /etc/NetworkManager/log-supplicant
 instructs NM to save the wpa_supplicant logs.  But that doesn't work:  we
 see wpa_supplicant invoked with the '-f' option, but without the required
 filename parameter.

-- 
Ticket URL: <http://dev.laptop.org/ticket/8799#comment:18>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system