From: "Linus Lüssing" <linus.luessing@c0d3.blue>
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.] ICMP6 flood or nodes limit ?
Date: Thu, 26 Jul 2018 09:24:01 +0200 [thread overview]
Message-ID: <20180726072401.GA1557@otheros> (raw)
In-Reply-To: <CALb7xhwsssLtKnT+Y8pmVch7OOUdUQ_n+yN61tUfQx7RE0KOCw@mail.gmail.com>
On Wed, Jul 25, 2018 at 10:50:10PM +0300, Nicu Pavel wrote:
> root@gateway-b827ebecbfa7:~# batctl o
> [B.A.T.M.A.N. adv 2018.2, MainIF/MAC: wlan0/b8:27:eb:ec:bf:a7 (bat0/4e:06:5f:54:e5:d5 BATMAN_IV)]
> Originator last-seen (#/255) Nexthop [outgoingIF]
> b8:27:eb:a7:ed:ff 0.330s ( 24) b8:27:eb:ad:4b:7e [ wlan0]
> b8:27:eb:a7:ed:ff 0.330s ( 0) b8:27:eb:ec:e5:9f [ wlan0]
> b8:27:eb:a7:ed:ff 0.330s ( 43) b8:27:eb:97:55:b6 [ wlan0]
> b8:27:eb:a7:ed:ff 0.330s ( 38) b8:27:eb:1b:61:f0 [ wlan0]
> b8:27:eb:a7:ed:ff 0.330s ( 15) b8:27:eb:91:5c:41 [ wlan0]
[...]
Overall, the TQ values seem rather low.
> root@gateway-b827ebecbfa7:~# batctl n
> [B.A.T.M.A.N. adv 2018.2, MainIF/MAC: wlan0/b8:27:eb:ec:bf:a7 (bat0/4e:06:5f:54:e5:d5 BATMAN_IV)]
> IF Neighbor last-seen
> wlan0 b8:27:eb:ad:df:c0 1.000s
> wlan0 b8:27:eb:30:15:c9 0.390s
> wlan0 b8:27:eb:a8:22:f6 1.560s
> wlan0 b8:27:eb:92:eb:b8 0.650s
[...]
> wlan0 b8:27:eb:bb:a1:94 11.710s
> wlan0 b8:27:eb:91:5c:41 1.480s
> wlan0 b8:27:eb:5f:eb:e8 7.600s
Those are quite a lot of neighbor nodes. Do you actually have any
airtime left? I can recommend H.O.R.S.T. to check that:
https://github.com/br101/horst
As a rule of thumb, BATMAN IV overhead increases linear to the
overall number of mesh nodes, but squared to the number of
neighbor nodes a particular node has.
Also, just to be on the safe side, check that there is no MAC
address conflict / duplicate MAC address somewhere.
Regards, Linus
prev parent reply other threads:[~2018-07-26 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 19:50 [B.A.T.M.A.N.] ICMP6 flood or nodes limit ? Nicu Pavel
2018-07-26 1:12 ` Marek Lindner
2018-07-26 6:14 ` Nicu Pavel
2018-07-29 15:38 ` Marek Lindner
2018-07-26 7:24 ` Linus Lüssing [this message]
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=20180726072401.GA1557@otheros \
--to=linus.luessing@c0d3.blue \
--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