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: Alessandro Bolletta <abolletta@netter.io>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: Running multiple batman-adv namespaces on the same broadcast domain
Date: Wed, 09 Sep 2020 11:05:11 +0200	[thread overview]
Message-ID: <7459754.hIpYFi07Vt@ripper> (raw)
In-Reply-To: <CADJ1cUSff_g-tB28HHeR5GrYHHtch7f+bdQQ85HdZx4dhLdTvw@mail.gmail.com>

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

On Wednesday, 9 September 2020 10:50:24 CEST Alessandro Bolletta wrote:
[...]
> Great, this is exactly what I'm looking for! I'm running this for some
> experimental purposes. Are you running VXLANs in multicast modes?

I am using it between datacenters with handcrafted forwarding rules. And I am 
using gluon which uses link local "multicast" mode [1]. 

[...]
> > I don't like the word "namespaces" here. Because this reverse to a completely
> > different concept in the linux kernel.
> >
> 
> Yeah, I'm sorry but I didn't know how to call them. "Mesh clouds" is a
> more exact term to call our batX?

I would call them batadv interfaces. And the thing behind it - maybe mesh 
cloud.

> > And I don't know what you will end using - so I cannot say if this will work
> > or is tested.
> >
> 
> I will use them in a scenario where a have 3 hosts connected by an
> ethernet card each and a switch. Then, I have to connect at layer 2
> these hosts to batman, but I need to separate their traffic through
> different batman-adv "mesh clouds" (in my case I can't use VLANs, QinQ
> or stuff like that to do so)

I've already used both VLAN and VXLAN (and other things) for stuff like this. 
But there can always be problems with your kernel/driver/batman-adv/... 
version or even the hardware. And I can guarantee that all of them will 
create some kind of cost (overhead, performance, ...).

Kind regards,
	Sven

[1] https://github.com/freifunk-gluon/gluon/blob/dd76e0898d70a123d8e7f178384fec84890e5251/package/gluon-core/files/lib/netifd/proto/gluon_wired.sh#L39

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

      reply	other threads:[~2020-09-09  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 11:23 Running multiple batman-adv namespaces on the same broadcast domain Alessandro Bolletta
2020-09-08 11:28 ` Sven Eckelmann
2020-09-09  8:20   ` Alessandro Bolletta
2020-09-09  8:30     ` Sven Eckelmann
2020-09-09  8:50       ` Alessandro Bolletta
2020-09-09  9:05         ` 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=7459754.hIpYFi07Vt@ripper \
    --to=sven@narfation.org \
    --cc=abolletta@netter.io \
    --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