public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: 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: Sat, 05 Nov 2016 09:31:10 +0100	[thread overview]
Message-ID: <2647191.IP1m5t5WQf@sven-edge> (raw)
In-Reply-To: <32cfb197-7944-7b9c-0d1c-6f6267d355de@t-online.de>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

On Freitag, 4. November 2016 22:37:24 CET Jean-Jacques Sarton wrote:
> Hello,
> 
> I have take a look to the configuration of our gateways.
> Inho there are some points which are not OK,
> Broadcasts are rebroadecasted on a wired connection,
> this seem for me to be an issue.

No, this is even required on some "wired" connections. For example Matthias 
Schiffer was against a change to remove rebroadcasts from the incoming 
interface when it is not a wifi interface. He requires it because his fastd is 
using non-wifi (so it basically a wired) interfaces. But it doesn't take care 
of any broadcast distributions for data which is incoming. He is relying on 
the fact that broadcast/multicast data he sends from a client to the fastd 
server is automatically rebroadcasted back once to the incoming interface. 
This will then force fastd to send this data to all its clients.

You also don't know what is actually behind the wireless device. So you can 
easily build a setup (yes, I have already seen this) which has a non-
transitive ethernet to ethernet-like bridge device which attaches via a second 
ethernet to the unit running batman-adv. Not rebroadcasting here would again 
create missing broadcast problems like with the standard wifi hidden node 
setups.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

      parent reply	other threads:[~2016-11-05  8:31 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
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 [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=2647191.IP1m5t5WQf@sven-edge \
    --to=sven@narfation.org \
    --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