[Commotion-admin] [commotion-linux-py] olsrd fails to get routes when multiple mesh networks are present (#14)

technosopher notifications at github.com
Mon Jan 27 19:40:25 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hrm... that doesn't surprise me at all, and is wholly consistent with
the channel-hopping hypothesis.  Nevertheless, I'm pretty sure I've
encountered a case in which I could establish a link to another meshed
device, but olsrd still refused to get any routes.  I think we may be
able to get a clearer picture of what's going on by doing the following:


1.  Set up isolated test meshes far away from any other
potentially-conflicting meshes, and see if we can reproduce this
problem.

2.  Try a variety of different mesh settings to determine which
parameters need to be unique to ensure that this doesn't happen (ie,
can meshes coexist as long as they have different ssids, BSSIDs, AND
channels?   Or is that not enough?)

3.  In failure cases, forcibly try to connect to other present mesh
nodes (ping and ssh to known-good ips).  If this consistently fails,
then the problem is almost certainly a link-layer issue.  If this
works sometimes, we can't rule out some sort of interaction involving
olsrd itself.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJS5rYdAAoJEL+9ounAjYBC0rwH/2SaY1Y3M1XIXBRXjM8BTE8c
1L8Te8PCqnqne30ioM+l/8U9G1q5+KyXQaow1nSNkBrjwCj0P9HVkWESpmIFxIyN
4U6u48cmXQ9PtdFi/thu0/ubBfMZqz1jTzI3at55Hdy0BF49Gx3XiA7RM1hQeOZn
wvnDxAVVYAYCjVpzM8Vxn9rQ9oMii1PeeW9ocXpUuj8mP3BoM6OqRFQSuQ+wpnhU
bsalVGd919ZakUnABsI5TQZzpq2ajvJ9LKtBjTywP8W78d2n79jpCQvySbLBxVVk
uohGkIDrBWxjnwixZjViijfkywAx8GtECR5NiRSKEqj0wBgJ/T+RCP+dNNGR6kw=
=rTIb
-----END PGP SIGNATURE-----

---
Reply to this email directly or view it on GitHub:
https://github.com/opentechinstitute/commotion-linux-py/issues/14#issuecomment-33412398
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-admin/attachments/20140127/6674e70d/attachment.html>


More information about the Commotion-admin mailing list