Mesh testing on a cluster

[Brian DeLacey]

Hi Francesco,
Our short term goal is to get 15 mesh points working on a cluster. Then we
can mesh in another half-dozen or more laptops, and eventually some
additional machines.

We looked to Netpipe as a testing tool ... but haven't quite got that
working yet. We're also developing some automated tests using Python. We
could really use a good mesh-management tool based on IW - so trying to get
some ideas going around that.

We plan to try a NAT to bridge over to the internet. I''ve been told it's
easy to do :)

We plan to try bridging meshes, using the MPP instructions at the end of the
HowTo <http://www.open80211s.org/trac/wiki/HOWTO> .

You have some really interesting and varied testing under way. It's great to
hear how that's going!

Brian


2009/3/16 Francesco <francesco.cappuccio at gmail.com>

> Network manager was evil for me...on all machines involved in my tests I
> wipe it away, installed wicd instead or configured it by hand.
> Actually I managed to send on network some traffic generated with mgen, to
> see how paths through nodes are chosen.Made some measurements. Pretty cool
> except for that program is a little buggy..
> Now I'm gonna see how the mesh behave with much more different shaped
> traffic, video (tried a divx multicast and works like a charm :-) ), voip
> and so on...
>
> Brian how many nodes were you able to interconnect?
> Did you get to use brdges among different mesh or all nodes belong to the
> same one?
>
> In case thing changed I ask again if anyone did succed into bridging the
> mesh with Internet...any piece of code would be really appreciated :)
>
>
>
> 2009/3/16 Brian DeLacey <bdelacey at gmail.com>
>
>> We made progress today getting a test mesh configuration established on a
>> cluster. So far, we've only done a few basic tests, pinging nodes on the
>> cluster, across the mesh but things are working well.
>>
>> We have a rack of clustered PCs and we've been able to ping those, via
>> multiple hops, from laptops outside the cluster. The tricky part was how to
>> test these remotely. We had to figure out a way to get around the usual
>> first step, which is typically to "killall NetworkManager" so that we could
>> continue to test via ssh remote logins. Thank you, Andrey, for providing the
>> suggestion on how to handle this:
>>
>> Problem > Is there any way (or hope) to run mesh tests without
>> shutting down NM? The cluster of computers we have access to has ongoing
>> uptime demand.
>>
>> Solution > Tell NetworkManager to ignore the mesh interface, and the
>> mesh-capable WiFi interface in general.  It's ok to have NM running as long
>> as it leaves our mesh interface alone, otherwise it brings it up/down, tries
>> to scan, etc.
>>
>> Now we move on to more advanced testing ...
>>
>> Brian
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.open80211s.org
>> http://open80211s.com/mailman/listinfo/devel
>>
>>
>
>
> --
> Francesco Cappuccio
>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.open80211s.org
> http://open80211s.com/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://open80211s.com/pipermail/devel/attachments/20090316/e7f0bd2a/attachment-0001.html