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.] Batman an more than one Gateway
Date: Sun, 6 Nov 2016 18:50:07 +0100 [thread overview]
Message-ID: <20161106175007.GE9484@otheros> (raw)
In-Reply-To: <7866334.t3BPe0EmV2@sven-edge>
On Sat, Nov 05, 2016 at 11:25:38PM +0100, Sven Eckelmann wrote:
> This can be wrong (as explained in my last mail). Gluon only sets the
> no_rebroadcast on the Freifunk router because it doesn't have to handle
> distribution of broadcast to multiple fastd endpoints. It would be
> completely wrong when set on the fastd server (handling multiple clients).
> See my other mail for details.
Just as a small addition, I think I've said it in the ticket, too:
Jean-Jacques, in one point, you're absolutely right:
When there is just one neighbor on an interface, then rebroadcasts
can easily be avoided. Which is the case in your scenario on the
VPN client(!) side.
Gluon has this extra patch for batman-adv, this no_rebroadcast
knob. But an automatic detection which should cover this specific
VPN client case, was merged into upstream batman-adv just a few
days ago \o/ :).
For any case with more than one neighbor on an interface it is
very hard to detect whether upon receiving a broadcast all other
neighbors have received this broadcast too.
If we can't say for sure, then we unfortunately need to stay safe
and rebroadcast to avoid horrible packet loss / broken connections /
armageddon.
next prev parent reply other threads:[~2016-11-06 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 21:37 [B.A.T.M.A.N.] Batman an more than one Gateway Jean-Jacques Sarton
2016-11-05 3:14 ` Marek Lindner
2016-11-05 21:29 ` Jean-Jacques Sarton
2016-11-05 22:25 ` Sven Eckelmann
2016-11-06 17:50 ` Linus Lüssing [this message]
2016-11-07 21:48 ` Jean-Jacques Sarton
2016-11-07 22:03 ` Jean-Jacques Sarton
2016-11-08 8:47 ` Simon Wunderlich
2016-11-07 6:45 ` Jean-Jacques Sarton
2016-11-07 8:02 ` Sven Eckelmann
2016-11-07 10:20 ` Jean-Jacques Sarton
2016-11-05 8:31 ` Sven Eckelmann
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=20161106175007.GE9484@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