[Trac #1005] Ping failure in a 13 Node mesh (adhoc) scenario.

[Zarro Boogs per Child]

#1005: Ping failure in a 13 Node mesh (adhoc) scenario.
----------------------+-----------------------------------------------------
 Reporter:  rchokshi  |        Owner:  jcardona 
     Type:  defect    |       Status:  assigned 
 Priority:  normal    |    Milestone:  Untriaged
Component:  wireless  |   Resolution:           
 Keywords:            |  
----------------------+-----------------------------------------------------
Comment (by luisca):

 Subir,

 we need you to be more descriptive about your test results. Were all nodes
 failing to ping or only the three nodes that transitioned into managed
 mode stopped pinging? In the latter, case, this would be just a duplicate
 of bug #972, transitioning to managed mode will most likely change the rf
 channel and will prevent the nodes from communicating with the others.
 Setting a new non-existent ad-hoc essid should fix it. It is also possible
 that the nodes entered frozen mode (#914) or crashed (like #526, maybe due
 to a different cause), which are separate bugs too.

 It would be useful too if you describe what nodes can or cannot do when
 they do not work, whether the node resolve IPs to MACs, whether other
 nodes can resolve the IP of the broken node, the ping succeeds if you
 manually add a direct route, and so on.

-- 
Ticket URL: <http://dev.laptop.org/ticket/1005#comment:16>
One Laptop Per Child <http://laptop.org/>