#8956 NORM Not Tri: mesh 11 connected but then was taken down

[Zarro Boogs per Child]

#8956: mesh 11 connected but then was taken down
--------------------------+-------------------------------------------------
 Reporter:  mikus         |                 Owner:               
     Type:  defect        |                Status:  new          
 Priority:  normal        |             Milestone:  Not Triaged  
Component:  not assigned  |               Version:  not specified
 Keywords:                |           Next_action:  never set    
 Verified:  0             |   Deployment_affected:               
Blockedby:                |              Blocking:               
--------------------------+-------------------------------------------------
 767.  Wanted a "mesh" at my house.  Booted one XO (it is not connected
 wired; it is not connected to any wireless AP).  Manually clicked on Mesh
 11 in Neighborhood.  Its 'Frame' shows mesh 11 connected.  Started 'Chat',
 asked to share it with neighborhood.

 Booted second XO (it is connected to wired ethernet; it is not connected
 to any wireless AP).  Manually clicked on Mesh 11 in Neighborhood.
 Eventually its 'Frame' showed mesh 11 connected.  Clicked on 'Chat' icon
 in Neighborhood.  Sent chat messages between the two XOs.

 Noticed that the second XO 'Frame' no longer showed connection icon.  Took
 olpc-dump on second XO.  Iwconfig on second XO shows that it is now trying
 to listen on channel 1.  'Chat' no longer transfers messages between the
 two XOs.  [Eventually, 'Chat' on the first XO put up a message saying the
 second XO had left the chat.]

 If the mesh is not permitted to co-exist with the ethernet, the XO should
 have prevented setting up the mesh, instead of letting the mesh work for
 some minutes, and only then taking it down.

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