#5146 BLOC Ship.2: Network Manager should not bring up the mesh automatically.

[Zarro Boogs per Child]

#5146: Network Manager should not bring up the mesh automatically.
------------------------------+---------------------------------------------
  Reporter:  jg               |       Owner:  dcbw  
      Type:  defect           |      Status:  new   
  Priority:  blocker          |   Milestone:  Ship.2
 Component:  network manager  |     Version:        
Resolution:                   |    Keywords:        
  Verified:  0                |  
------------------------------+---------------------------------------------

Comment(by gnu):

 If clicking on Mesh Circle 6 results in "standalone mesh on channel 1",
 wouldn't that be a problem?

 Better defined new behavior:

   *  At startup, do nothing by default.
      * If a previous configuration is saved, then attempt to re-establish
 that configuration.

   *  When a mesh circle is clicked on:
      *  Disassociate with any access point.
      *  enable mesh on that channel
      *  Look for school server on that channel; if none,
      *  Look for XO portal on that channel; if none,
      *  Retain a standalone mesh on that channel

   *  When an access point is clicked on:
      *  disable mesh
      *  Try to associate to that AP.
      *  If that fails, disable normal wireless and mesh.

   *  When a new "No wireless" icon is clicked on:
      *  Disable mesh, disable normal wireless.

 This would also fix #1406 (airplane mode).  And it would make the
 inscrutable Network Manager much more straightforward for users.  (Except
 that this doesn't document what happens when a wired Ethernet shows up.)

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