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 10:30:19 +0200 [thread overview]
Message-ID: <34120415.8pMx1AJBNe@ripper> (raw)
In-Reply-To: <CADJ1cUSNtDrR-C-L7MHXF3JohbkmBbQBsFzBvBxE2WntUd9Yqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
On Wednesday, 9 September 2020 10:20:20 CEST Alessandro Bolletta wrote:
> Just one more info: is there an hard limit for the number of "bat"
> interfaces on the same host?
But yes, running multiple batman-adv interfaces on the same host works fine. I
am currently using 8 in parallel. The lower/hardif/slave interfaces are using
VXLAN (to connect some servers in other datacenters), fastd (to connect remote
"clients") and some other "ethernet" protocol compatible things.
And the hard limit is most likely the number of netdev's the Linux kernel can
create (id wise and memory wise).
> Moreover, is the multiple batX namespaces a scenario that it is
> supposed to work fine, is it well tested or it still does need some
> love?
I don't like the word "namespaces" here. Because this reverse to a completely
different concept in the linux kernel.
And I don't know what you will end using - so I cannot say if this will work
or is tested.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-09 8:30 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 [this message]
2020-09-09 8:50 ` Alessandro Bolletta
2020-09-09 9:05 ` 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=34120415.8pMx1AJBNe@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