From: Sven Eckelmann <sven@narfation.org>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>,
umut deniz <umut.deniz@gmail.com>
Subject: Re: [B.A.T.M.A.N.] Fwd: nodes start disappearing after a certain node count
Date: Mon, 25 Feb 2019 17:50:08 +0100 [thread overview]
Message-ID: <59660839.RxU627SyFe@bentobox> (raw)
In-Reply-To: <20190225160046.GD1761@otheros>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Monday, 25 February 2019 17:00:46 CET Linus Lüssing wrote:
[...]
> Disable batman-adv and try a broadcast ping like "ping6 ff02::1%adhoc0" and
> unicast ones. If that works with 6 nodes, but not with 7 ones then you
> know it's not batman-adv's fault.
This is only true when the driver/firmware handles multicast frames as
broadcasts. I have already seen some of them converting the multicast/unicast
frames to unicast frames in such situations. This also broke OGM detection on
batman-adv because we only accept broadcast OGMs received as broadcast -
otherwise the OGM metric stuff wouldn't make any sense at all.
And you have to do this in both directions to check whether bidirectional
links are available. A ping6 answer (icmp echo reply) is unicast - and you
also need the check the broadcast stuff in both direction.
But yes, when even this test fails then it is definitely not batman-adv's
fault. Just keep in mind that a working ping6 doesn't have to mean that it is
batman-adv's fault.
Kind regard,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-02-25 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHh66V8N6KCqGdxnMQpHTaqjLbfMwWyGrRvjZY+P20W3-UF4Hw@mail.gmail.com>
2019-02-24 20:48 ` [B.A.T.M.A.N.] Fwd: nodes start disappearing after a certain node count umut deniz
2019-02-24 21:22 ` Sven Eckelmann
2019-02-25 14:06 ` umut deniz
2019-02-25 14:19 ` Sven Eckelmann
2019-02-25 16:00 ` Linus Lüssing
2019-02-25 16:50 ` Sven Eckelmann [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=59660839.RxU627SyFe@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=linus.luessing@c0d3.blue \
--cc=umut.deniz@gmail.com \
/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