[Trac #1005] Ping failure in a 13 Node mesh (adhoc) scenario.
Zarro Boogs per Child
bugtracker at laptop.org
Wed Mar 7 20:05:50 EST 2007
#1005: Ping failure in a 13 Node mesh (adhoc) scenario.
----------------------+-----------------------------------------------------
Reporter: rchokshi | Owner: jcardona
Type: defect | Status: assigned
Priority: normal | Milestone: Untriaged
Component: distro | Resolution:
Keywords: |
----------------------+-----------------------------------------------------
Comment (by jcardona):
Able to reproduce this at OLPC testbed at 7:30 PM Boston time (can that be
considered a noisy hour?).
Captured the state on the two nodes that could not ping each other.
Confirmed that pinging other nodes still works. The nodes that could not
ping each other were meshy5 and meshy7. Looking at the forwarding tables,
one can see that there is no direct route from meshy7 to meshy5. Adding a
direct route manually resolved restored the pings.
{{{
From mshy5 (10.2.51.50) icmp_seq=4427 Destination Host Unreachable
From mshy5 (10.2.51.50) icmp_seq=4429 Destination Host Unreachable
From mshy5 (10.2.51.50) icmp_seq=4430 Destination Host Unreachable
From mshy5 (10.2.51.50) icmp_seq=4431 Destination Host Unreachable
64 bytes from mshy7 (10.2.48.17): icmp_seq=4432 ttl=64 time=1772 ms
64 bytes from mshy7 (10.2.48.17): icmp_seq=4433 ttl=64 time=772 ms
64 bytes from mshy7 (10.2.48.17): icmp_seq=4434 ttl=64 time=14.8 ms
64 bytes from mshy7 (10.2.48.17): icmp_seq=4435 ttl=64 time=7.24 ms
}}}
Resetting the forwarding table at meshy7. Able to ping mshy1 (route
rediscovered), but not mshy5.
--
Ticket URL: <http://dev.laptop.org/ticket/1005#comment:5>
One Laptop Per Child <http://laptop.org/>
More information about the Bugs
mailing list