From: "Nicolás Echániz" <nicoechaniz@altermundi.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] mad mad batman ...
Date: Tue, 26 Nov 2013 00:56:29 -0300 [thread overview]
Message-ID: <52941BED.9070402@altermundi.net> (raw)
In-Reply-To: <20131113080157.GO3713@neomailbox.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El 13/11/13 05:01, Antonio Quartulli escribió:
> On Wed, Nov 13, 2013 at 09:04:05AM +0100, Bastian Bittorf wrote:
>> * Nicolás Echániz <nicoechaniz@altermundi.net> [13.11.2013
>> 08:59]:
>>> Am I the only one who has bumped into this (twice)?
>>
>> I have also seen a lot of these messages with an indoor mesh, so
>> no lightning involved 8-) but with v2013.04 this is gone. (same
>> network).
>
> this message is the symptom of a loop. The causes can be
> gazillions.
Well... it took about a week to finally find the node creating this
problem. As before, it's failing hardware that caused the issue.
When this happens every node in the net is repeatedly showing that
message. It is not the same with any "loop symptom" I believe... At
least I've never seen this happen on every node being caused by
something else.
I really would like to find out more about how this condition comes to
happen and how to diagnose and prevent it. The whole batman-adv cloud
dies when this happens and it's a pain in the ass to "debug".
All the failing routers are WR842ND. There are many more of the same
model working just fine.
I now have three routers which produce this symptom, so if anyone who
can understand the problem better is willing to test, I can set up a
dedicated mini-test-bed.
Cheers,
NicoEchániz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQEcBAEBAgAGBQJSlBvtAAoJEPHORz17N0TFf+sH/jC2qGbx3SpHZSNGgUoQrD/f
J9n+lUMugbsM7uOodBnU+iiswpOrNVn4NsddWNYXFmydpbIbnO6wuUTlDZu3wNig
gOMNDZqaze5fcdopwgcEuxvp1S5QRiAe2DN+ci0jQ3OGdOjuZgZJjpRxARDbSExT
guF4TgB4izZUy5/5OTg4pJdNZ8zUsMap45Gy4xzslP58EZUBKkeqol+kaWuiq4eX
FbUpezTpeTXlUi401pOzvrVMg7/JXhN7JULMgjPPR6y8359tfZFFQq4JwuYNSwz1
Fg6L3/kJSKm4DF7MyYa2Id/3DJx7NLZk1B7RQR05ISmuvGLDBqobqv6EY5a+Z0M=
=0BD+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-11-26 3:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 21:34 [B.A.T.M.A.N.] mad mad batman Nicolás Echániz
2013-11-12 21:45 ` Nicolás Echániz
2013-11-12 21:54 ` Antonio Quartulli
2013-11-13 0:56 ` Nicolás Echániz
2013-11-13 8:04 ` Bastian Bittorf
2013-11-13 8:01 ` Antonio Quartulli
2013-11-26 3:56 ` Nicolás Echániz [this message]
2013-11-26 4:48 ` Linus Lüssing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52941BED.9070402@altermundi.net \
--to=nicoechaniz@altermundi.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox