Il giorno mer 9 set 2020 alle ore 10:30 Sven Eckelmann sven@narfation.org ha scritto:
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.
Great, this is exactly what I'm looking for! I'm running this for some experimental purposes. Are you running VXLANs in multicast modes?
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.
Yeah, I'm sorry but I didn't know how to call them. "Mesh clouds" is a more exact term to call our batX?
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)
Kind regards, Sven