Cluster test update

[Brian DeLacey]

I had a chance to get started installing mesh on a cluster over the weekend.
The cluster is now remotely accessible and we have a number of wireless
adapters plugged in. It will take a while to make our way through the
configuration before we see test results. I'll provide an update when we do
...

I expect I'll be able to get some good bandwidth tests on this cluster, but
it looks like I won't be able to do "packet path tracking" without
instrumented code. I found Python programs for ping and traceroute. Perhaps
these could be modified for automated testing? The codebase looks good, but
it is old and would need to be revived in order to work with current
versions of Python. Here's a description in case anyone is interested:

"code for manipulating raw IP, ICMP, and UDP packets. They allow you to
write ping and traceroute completely in Python; the code is smaller and
simpler than the corresponding C versions (e.g.
traceroute.c<ftp://ftp.aces.com/software/traceroute/traceroute.c>).
The code was written for Python 1.4; it should be updated... "
Source: http://www.python.org/~jeremy/python.html

I did some "mobile" testing with three mesh-connected computers wandering
around a building. Things worked quite well, with the mesh routes changing
appropriately as the systems passed in and out of range and reset their
paths. We saw quick reconnects whenever "lost" radios returned within range.


It would be very helpful to have a mesh management utility that could show
mac address / ip address / mesh path and mesh station dump information as a
real-time report dashboard.  There's a lot of good info about the mesh
configuration spread across several utilities, e.g. IW, IFCONFIG, IWLIST,
IWCONFIG.  Maybe it could be pulled together into one display? Has anyone
tried anything like this?

Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://open80211s.com/pipermail/devel/attachments/20090309/a667bc85/attachment.html