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

 I discussed this with Dan in irc. I'm going to summarize the plan here.

 Current automatic logic in NM:

    1. use the mesh device, find a server on channel 1, then try channel 6,
 then 11
    2. if that fails, let the infrastructure ethX interface try to connect
 to a known WiFi? AP
    3. if that fails, start looking for XO mesh portals
    4. if that fails, just activate the mesh on channel 1

 Current manual login in NM (triggered by SetActiveDevice? when the user
 click on a mesh icon):

    1. look for school server on that channel
    2. look for an XO portal on that channel
    3. standalone mesh on channel 1

 The plan is to disable automatic connection altogether and keep the same
 logic for manual connection. Additionally, once the driver interface
 allows it, NM will turn the mesh on when it activates the device in stage
 1, and turn the mesh off when it deactivates the device.

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