[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 swagle at marvell.com):

 Javier,

 Only the three nodes transitioning into the managed mode stopped pinging.
 These nodes displed the error Destination Host Unreachable for a while and
 later on move into the ping buffer overflow mode.From this point it is not
 possible to recover the node and the only way is to restart the mesh mode
 on the node using the command

 iwconfig msh0 mode ad- essid a

 One interesting point that I saw when I restarted the node is that it
 still fails to ping the node it was earlier pinging.I have to manually
 delete the arp entry from the table only after which the ping resumes.The
 restarted node can ping any other node in the mesh since the arp entry for
 the other node is not present.

 I did not see the problem of the node staying in the ad-hoc mode and
 failing on the ping as we used to see earlier.I'm planning to increase the
 number of nodes and repeat this test.Please let me know if you need any
 other information.

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