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

Zarro Boogs per Child bugtracker at laptop.org
Fri Nov 7 22:16:40 EST 2008

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

 Replying to [comment:16 jcardona]:
 > We are working on a fix in NM.
 In fact, it is possible to fix this in the driver by eliminating networks
 with all-zero BSSID in scan results.  This is implemented in this patch:

 But because the all-zero BSSIDs is a valid BSSID, I would recommend
 assigning an invalid BSSID (e.g. all ones) to uninitialized networks
 instead of all-zeros.

 The patch that worked for us in NM was:
 Index: src/nm-dbus-nmi.c
 --- src/nm-dbus-nmi.c   (revision 4233)
 +++ src/nm-dbus-nmi.c   (working copy)
 @@ -458,6 +458,10 @@
         /* Construct the new access point */
         ap = nm_ap_new ();
         nm_ap_set_essid (ap, essid);
 +       struct ether_addr invalid_bssid = { {0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
 0xFF} };
 +       nm_ap_set_address (ap, &invalid_bssid);
         nm_ap_set_security (ap, security);
         g_object_unref (G_OBJECT (security));   /* set_security copies the
 object */

 So either patch (or both) will address the problem we were seeing of
 Association Requests for WPA access points being issued with invalid
 security information.

 While working on this ticket, we uncovered a number of other issues:

  1. redundant WPA key removals
  2. under some conditions the association work queue would be executed
 with nothing to do
  3. WPA key installation coupled with delayed association work queue
  4. wpa_supplicant clearing the BSSID would result in association requests
 to 'any' AP, adding unnecessary delays to WPA associations.

 The patches posted here address these issues:

 With this patches things improve a lot:  we are now always able to
 associate via the GUI, but sometimes it requires a few retries (more about
 this in a separate post).

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

More information about the Bugs mailing list