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

 These are the remaining failure modes that we currently see:

 FM#1: keys do not get installed, AP sends deauth frame, firmware triggers
 deauth event (8)
 FM#2: sta sends deauth frame to the AP, reason code "STA leaving" (3)
 FM#3: there is no association command ever sent to the firmware (as if AP
 did not show up in scan results, but the AP appears in the scan logs)
 FM#4: transition from 4-WAY_HANDSHAKE -> ASSOCIATED

 This is with firmware version 5.110.22.p22 and latest driver from testing
 branch.  As previously reported, these failures are only observed when
 associating via the GUI to a WAP AP.

 One hypothesis:  we see scans taking place while associating.  The
 association command is handled atomically by the firmware, but not the WPA
 authentication.  If we scan in other channels during WPA authentication,
 we could miss EAPOL frames, which would have the same symptoms as FM#1 and
 possibly FM#2.

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