From: Matthias Schiffer <mschiffer@universe-factory.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.] [RFC 2/2] batman-adv: Don't re-broadcast packets on non-wifi devices
Date: Thu, 31 Mar 2016 10:41:04 +0200 [thread overview]
Message-ID: <56FCE2A0.7000200@universe-factory.net> (raw)
In-Reply-To: <1459340372-6971-2-git-send-email-sven@narfation.org>
[-- Attachment #1.1: Type: text/plain, Size: 960 bytes --]
On 03/30/2016 02:19 PM, Sven Eckelmann wrote:
> It is not necessary to re-broadcast a received broadcast packet on the
> rx-device when it is a standard ethernet device. The link medium already
> takes care of transporting it to all participants in the broadcast domain.
>
> The re-broadcast on other devices is still necessary to allow the broadcast
> packet to be received by devices which are using a different link medium.
>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
I don't think completely disabling the rebroadcast here without a way to
enable it again is a viable option.
At least when using batman-adv over VPN tunnels, making batman-adv take
care of establishing transitive connectivity may make sense, as batman-adv
does this very well and without much configuration. This is actually the
recommended setup for non-full-mesh setups using the VPN tool fastd (which
is developed by me.)
Regards,
Matthias
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-31 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 12:19 [B.A.T.M.A.N.] [RFC 1/2] batman-adv: Split the setting for number re-broadcasts Sven Eckelmann
2016-03-30 12:19 ` [B.A.T.M.A.N.] [RFC 2/2] batman-adv: Don't re-broadcast packets on non-wifi devices Sven Eckelmann
2016-03-31 8:41 ` Matthias Schiffer [this message]
2016-03-31 9:07 ` 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=56FCE2A0.7000200@universe-factory.net \
--to=mschiffer@universe-factory.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