#2316 NORM Untriag: Laptops don't mesh together if they choose different channels

[Zarro Boogs per Child]

#2316: Laptops don't mesh together if they choose different channels
-----------------------------+----------------------------------------------
 Reporter:  mcfletch         |       Owner:  dcbw     
     Type:  defect           |      Status:  new      
 Priority:  normal           |   Milestone:  Untriaged
Component:  network manager  |     Version:           
 Keywords:                   |    Verified:  0        
-----------------------------+----------------------------------------------
 Working with a B2 and a B3 on build 523 I'm seeing a situation where at
 one point (with many restarts at the like during testing) I had both
 machines seeing each other on the (local-only) mesh network, as we would
 expect and want.

 After a few more restarts I encountered a situation where the two laptops
 were unable to see each other at all (as distinct from one laptop seeing
 the other).  For two children in the field, this would seem to just be the
 two computers failing to see each other.  Looking into the situation, it
 seems the two laptops have set up their mesh networks on different
 frequencies/channels (as shown by iwconfig).

 While the problem could likely be fixed with an iwconfig command-line
 operation, it seems that we should have a way for the user to tell the
 network configuration to "try again", cycling through the available valid
 configurations until it finds a different one than was last chosen,
 cycling back to the first when it runs out of valid configurations.

 Even just a simple way to say "re-do mesh setup" would probably handle
 most such situations assuming we have a reasonable channel-choice
 heuristic.

 See also: #1865 #1323

-- 
Ticket URL: <https://dev.laptop.org/ticket/2316>
One Laptop Per Child <http://laptop.org/>