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: Batman adv selective broadcast mechanism
Date: Wed, 24 Mar 2021 14:27:21 +0100 [thread overview]
Message-ID: <20210324132721.GC2174@otheros> (raw)
In-Reply-To: <20210324121616.1198.15914@diktynna.open-mesh.org>
Hi,
On Wed, Mar 24, 2021 at 12:16:16PM -0000, oytunyapar@hotmail.com wrote:
> Hi everybody,
>
> As I check, batman-adv protocol, sends IP broadcast packets, to every slave interface, including the slave interface from which the broadcast packet is received. Is there any way for preventing the batman-adv from sending IP broadcast packets to some of the slave interfaces (etc. the one which the packet is received)?
When there is just a single neighbor on the interface a node
received the packet on that batman-adv avoids sending it
back automatically. E.g. this case here:
https://www.open-mesh.org/projects/batman-adv/wiki/Broadcast#IIII-Single-Neighbor-Is-Previous-Sender
If there are multiple neighbors on the receiving interface then
batman-adv assumes that other neighbors might potentially not have
received the packet from the original sender. And will therefore
rebroadcast on the incoming interface, too.
If you are 100% sure that all other neighbors received it from
the original sender then there is this old patch which isn't
upstream though (including the discussion with why it was
rejetected for upstream):
https://patchwork.open-mesh.org/project/b.a.t.m.a.n./patch/1380030033-11533-1-git-send-email-linus.luessing@web.de/
Regards, Linus
next prev parent reply other threads:[~2021-03-24 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 12:16 Batman adv selective broadcast mechanism oytunyapar
2021-03-24 13:27 ` Linus Lüssing [this message]
2021-03-25 12:58 ` oytunyapar
2021-03-28 21:18 ` Linus Lüssing
2021-03-31 9:06 ` oytunyapar
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=20210324132721.GC2174@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.