#2383 BLOC Untriag: Laptop not scanning for mesh; can't connect to the XO on an AP

[Zarro Boogs per Child]

#2383: Laptop not scanning for mesh; can't connect to the XO on an AP
------------------------------+---------------------------------------------
  Reporter:  kimquirk         |       Owner:  dcbw     
      Type:  defect           |      Status:  new      
  Priority:  blocker          |   Milestone:  Untriaged
 Component:  network manager  |     Version:           
Resolution:                   |    Keywords:           
  Verified:  0                |  
------------------------------+---------------------------------------------
Comment (by dcbw):

 There's two distinct issues here:

 1) A fix went into NetworkManager that will show up in the Sunday builds
 for scanning behavior.  NM was sometimes forgetting to scan when it should
 have.  Second, a kernel driver fix which Marcelo and I are verifying is
 needed to make the scan behavior less hacky, which compounded the
 NetworkManager problem that's already been fixed.  That should land on
 Monday (or Sunday if dilinger is around tonight).

 2) If an XO is connected to an encrypted access point, no other XOs will
 recognize and use that XO as an XO-MPP.  This is because when an XO is
 connected to an encrypted AP, _everything_ is encrypted, even the mesh for
 that XO.  So the other XOs have no idea what encryption key to use, nor do
 they have any idea how to pick a key.  Right now, they can pick the key
 based on SSID, but the mesh doesn't have SSIDs at all.  This is simply a
 limitation of the mesh right now, and is unlikely to be resolved any time
 soon.

 You can have two XOs on channel 6, on connected to an encrypted AP (and so
 that XO's mesh interface is also encrypted), and one connected to an
 unencrypted AP (so that XO's mesh interface is not encrypted).  The two
 XOs will _not_ be able to see each other at all.

 We are recommending that layer 2 (ie wireless layer) encryption _not_ be
 used.  We fully intend to encourage and use layer 3 (ie application layer)
 encryption/security.  Layer 2 encryption is not sufficient by itself
 anyway.

-- 
Ticket URL: <https://dev.laptop.org/ticket/2383#comment:1>
One Laptop Per Child <http://laptop.org/>