On Mittwoch, 16. August 2017 09:47:08 CEST dan wrote:
Can batman-adv carry a vlan? For example, 2 mesh nodes are directly connected via eth0 on both devices. bat0 contains eth0 on both devices.
batman-adv was able to transport 802.3Q tags (and similar mechanism) since the beginning. But there were some changes [1] in the past to make TT VLAN aware [2]. But this is only required when you have your clients connected to different batman-adv instances with different VLANs (for example AP1 has the client in VLAN 23 and the AP2 has the client in AP42).
The pre-2014.0.0 implementation has the benefit that the VLAN23 and VLAN42 don't have to be configured on top of bat0 to let batman-adv transport 802.3Q tagged frames for VLAN23 and VLAN42 [3]. But the new implementation has the benefit that an client entry on two different VLANs and two different batman-adv instances is not seen as conflict and just works out of the box. This is possible because client X + VLAN23 and client X + VLAN42 are handled since 2014.0.0 as two separate entries in TT.
Can a bat0.20 vlan be created on each side and will batman-adv pass traffic assuming 1532 MTU is set?
Don't forget that the 802.3Q VLAN header requires also 4 bytes [4].
Kind regards, Sven
[1] https://www.open-mesh.org/news/56 [2] https://www.open-mesh.org/projects/batman-adv/wiki/Client-announcement [3] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2017-February/016904.html [4] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2016-November/016676.html