Mesh testing

[Ricardo Carrano]

Pol,

I suggest you switch to 22.p10 which fixes a bug in 22.p9.
But you should not use any firmware later than 22.p6 with stock kernel
(because of the multicast filter, #6818). It surprises me that you are able
to collaborate at all.

--
Ricardo

On Mon, May 5, 2008 at 12:34 PM, Polychronis Ypodimatopoulos <ypod at mit.edu>
wrote:

> I 've been doing experiments on a 50-node testbed (703, Q2D14, 22.p9,
> simple mesh) and getting all 50 of them to communicate consistently has
> been hard, even in the absence no sharing or heavy workloads involved.
>
> Out of the 50 nodes (over a period of time of 6 hours), 8 nodes
> "decided" to take msh0 down, half of which did not come up again
> (NetworkManager?).
>
> About 18 out of 50 nodes (not including the previous 8) for some reason
> stopped being reachable from the rest of the network, although their
> network interface did not seem to have been reset. Restarting the
> NetworkManager seems to fix the problem.
>
> Is anyone still maintaining the NetworkManager? It seems to me that the
> NetworkManager chooses to restart msh0 sometimes. Is this true? Does it
> go so far as to reload the firmware?
>
> Pol
>
>
> --
> Polychronis Ypodimatopoulos
> Graduate student
> Viral Communications
> MIT Media Lab
> Tel: +1 (617) 459-6058
> http://www.mit.edu/~ypod/ <http://www.mit.edu/%7Eypod/>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080505/f05e791c/attachment.html>