On Wed, 11 Jun 2008, Trent Lloyd wrote: > Keep in mind however that the other traffic, i.e. discovering the > other XO is a multicast packet and therefor would be routed on the > mesh somewhat differently AIUI (its basically re-broadcasted by every > node?) > > Thus I suspect the issue is the nodes simply have no direct > communication at all given the lack of replies to the ARP packets.. > and any "other" tcp or ping is not going ot work if arps simply aren't > being replied to, as ARPs are in no way specific to the connection type. > > Thus I suspect the issue is that multicast forward is working (which > seems perfectly sane mentally, given what I know as the difference > between how unicast and multicast work on the mesh) but the direct > node-node path is totally broken and this would be a relatively > pointless excercise. > > I guess getting the mesh neighbour tables per Bill's email would be > the most useful step forward.
And arp tables, that will give the idea if ARP responses were received and used to correctly update the tables. -- Alex _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
