public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
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: Sat, 05 Nov 2016 11:14:50 +0800	[thread overview]
Message-ID: <2562442.4W30obIVjL@lafayette> (raw)
In-Reply-To: <32cfb197-7944-7b9c-0d1c-6f6267d355de@t-online.de>

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

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

Rebroadcast on an interface depends on the interface type. Generally, batman 
runs on 3 different types of interfaces:

 * WiFi: payload broadcasts are transmitted 3 times to increase the chances of 
a successful transmission
 * VPN / wired Ethernet: payload broadcast is transmitted once as most sane 
VPNs don't experience packet loss

Guessing from your interface names you are running VPNs and not wired 
Ethernet, is that correct ?


> this seem for me to be an issue.

What exactly is the issue ? 


>       Gateway      (#/255)           Nexthop [outgoingIF]: advertised uplink
> bandwidth ... [B.A.T.M.A.N. adv 2014.3.0, MainIF/MAC:
> ftun-q1/12:e8:ef:7f:0d:c8 (bat0)] ca:b1:f2:63:f3:cf (251) ca:b1:f2:63:f3:cf
> [   ftun-q1]: 50.0/50.0 MBit
> 
> [B.A.T.M.A.N. adv 2016.4, MainIF/MAC: mesh0/92:fb:53:11:44:f1
> (bat0/90:f6:52:11:44:f1 BATMAN_IV)] IF             Neighbor             
> last-seen
>      mesh-vpn	  aa:ff:ca:ca:fe:03    3.342s

It is recommended to run the same batman version on all nodes to avoid 
unexpected behavior. These 2 versions are separated by 2 years of development.


Cheers,
Marek

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

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

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=2562442.4W30obIVjL@lafayette \
    --to=mareklindner@neomailbox.ch \
    --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