Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2019-09-14,master

commit 53bb9e7f0b20221cb770f68fca4a76a4e8f8d8ca Author: Sven Eckelmann sven@narfation.org Date: Sat Feb 23 10:00:58 2019 +0000

doc: batman-adv/Faq: add section about vlan questions

53bb9e7f0b20221cb770f68fca4a76a4e8f8d8ca batman-adv/Faq.textile | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)

diff --git a/batman-adv/Faq.textile b/batman-adv/Faq.textile index 21bc9c3..a8783c8 100644 --- a/batman-adv/Faq.textile +++ b/batman-adv/Faq.textile @@ -142,3 +142,21 @@ h3. What about DHCP server for separate meshes?

*Q:* I would like to setup a DHCP server in separate meshes? _Or:_ How can I make two separate meshes use a single DHCP server (using gw_mode feature) in current blaII design? *A:* Each node at the edge to the wired network may announce itself as a gateway, provided that a DHCP server is available in the LAN (or any network behind it, e.g. a mesh). From a concept view, a gateway (or maybe even multiple gateways) in mesh2 will not automatically announced in mesh1 - this must be configured manually, or let batman use Ethernet if this is explicitly required. + + +h2. B.A.T.M.A.N. Advanced - VLAN questions + +h3. VLAN forwarding doesn't work + +*Q*: When I have a bridge which connects an ethernet devices with bat0, VLAN frames from the ethernet interfaces are not forwarded by batman-adv. How is it possible to forward these frames +*A*: batman-adv since 2014.0.0 is VLAN-aware. It is only able to forward VLAN frames when it knows about the VLAN. This can either be done by creating a VLAN device with the correct VID on top of the batadv (bat0) device: + +<pre> +ip link add link bat0 name bat0.23 type vlan id 23 +</pre> + +Or in case of a VLAN-aware bridge, it is better to add the correctly add the VLANs as required to the specific ports: + +<pre> +bridge vlan add vid 23 dev bat0 +</pre> \ No newline at end of file