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

 OK, we believe we've found the root cause for this.

 The sequence that leads to the failure is the following:

 1.  The NetworkManager applet will parse networks.cfg and pass the list of
 preferred networks to NetworkManager.

 2.  NM creates instances of network objects from the previous list.  The
 newly created network objects are initialized with BSSID set to all zeros.
 (The BSSID passed by the applet is actually saved in a different field,
 user_address).

 3.  A scan result comes in which includes a null-BSSID network (this will
 happen around mesh nodes, as mesh management frames have null-BSSID).

 4.  NM matches the scan results with the preferred network lists by BSSID.
 The properties of the null-BSSID network are assigned to all the networks
 in the preferred list.  If the AP we are trying to associate has some form
 of security, association will fail.

 We are working on a fix in NM.

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