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/dd76e0898d70a123d8e7f178384fec8...