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 23:25:38 +0100	[thread overview]
Message-ID: <7866334.t3BPe0EmV2@sven-edge> (raw)
In-Reply-To: <0b99a1f3-aa99-eb62-46cf-f959011a05e6@t-online.de>

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

On Samstag, 5. November 2016 22:29:19 CET Jean-Jacques Sarton wrote:
> Am 05.11.2016 um 04:14 schrieb Marek Lindner:
> > Hi,
> > 
> >> 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,
> > 
> > please note that batman's payload reboradcast behavior is unrelated to the 
> > batman gateway feature. The effect of the batman gateway feature is explained 
> > here: https://www.open-mesh.org/projects/batman-adv/wiki/Gateways
> > 
> This seem to work but for IPv6 there is nothing and the client get
> RA's from all GW.

The important message from Marek (we already told you this multiple
times) was:

"batman-adv gateway feature" has nothing to do with "rebroadcast".

So please stop mixing these things together in all your messages. It also
doesn't help when you now start to bring up IPv6 RAs. They are not IPv4
DHCP requests and are therefore as unrelated to the "batman-adv gateway
feature" as "rebroadcasts".

> > * VPN / wired Ethernet: payload broadcast is transmitted once as most sane 
> > VPNs don't experience packet loss
> 
> This what the interface type used. This mean that the gateway send
> a broadcast via wire and the node get it as if there where no VPN between
> GW and node. rebroadcasting is not OK here.

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.

Kind regards,
	Sven

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

  reply	other threads:[~2016-11-05 22:25 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 [this message]
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

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=7866334.t3BPe0EmV2@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