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

 > >   *  When a new "No wireless" icon is clicked on:
 > >      *  Disable mesh, disable normal wireless.
 >
 > The icon in the mesh view represent objects (access point, activity,
 buddy), they are not action buttons, so I don't think it would be
 appropriate there. We plan to add a preference in the control center for
 this.

 Well, yes and no. The current mesh icons don't really represent objects
 since they do not appear if there is mesh traffic sensed in that channel
 (the reason that we added the mesh beacons), they always appear and they
 represent a trigger for an action ("join mesh at channel X").

 We have to keep in mind the mesh implementation semantics:

 We have two logical interfaces and only one radio. (in the basic case,
 this changes if we add an external one - let's leave this out at this
 stage).
 This means that every time we start one interface at channel X, the other
 is bound to the same channel.

 We are keeping the mesh frame forwarding functionality running all the
 time (unless we explicitly need to turn it off).

 So when we associate with an AP using eth0, we are automatically
 forwarding mesh frames on the same channel (regardless of whether we use
 msh0 or not).

 If we explicitly start msh0 on a given channel, then we can automatically
 set eth0 to ad-hoc mode on the same channel (or even associate with an AP
 in that same channel)

 So when we click on an AP, we don't have to disable the mesh, we just move
 its operation to whatever channel the AP happens to be. If the MPP
 functionality is enabled we also become a mesh portal for that channel.

 If we click on a mesh icon the situation is a bit more complicated. If we
 are associated with an AP (let's forget the ad-hoc case for now) that's on
 the same channel with the intended mesh channel, nothing needs to happen
 at the radio level (we are already operating there anyway), we just need
 to go through the IP config dance (there is where preferences can play an
 important role). If it is a different channel, then the association has to
 stop before we move to the new mesh channel.

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