Option force_link 'yes' (Optional) /etc/bat-hosts The 2nd node should disable DHCP and sport a similar setup, the only difference is to use different IPs for the networks (lan: 192.168.1.254 and guest: 192.168.2.254 should use another IP in that subnet) # Guest network in VLAN 2, and bridged(as stated above) with Batman VLAN 2 # LAN with VLAN 1, and bridged(as stated above) with Batman VLAN 1 and all 4 Ethernet ports This is how bridges operate in Linux, in general, not an OpenWrt-specific limitation. As soon as a typical Ethernet-like interface is included, the MTU will be 1500 or less, even if one or more members of the bridge have a larger MTU. These bridges will have an MTU no larger than the smallest MTU of its bridged interfaces. There is the typical 15-character limit on interface names in the Linux kernel, which needs to include the br- prefix. If you are using IPv6, you should examine if this is the proper setting for your application.īy current convention, OpenWrt will name the interfaces for bridges by prefixing them with br- yielding br-vlan1111 and the like. The option delegate '0' “turns off” certain IPv6-related features on the interface. Multiple VLANs can be bridged/routed over a single batman-adv interface. With batman-adv now able to route packets among peers, the remaining step is to use that facility to route “useful” traffic.Īs appropriate for each node, edit /etc/config/network based on these examples. Please consult other documentation for details of those operations as they may apply to your situation. Note: This does not discuss how to configure switches for VLANs, associate wireless interfaces with bridges, or firewall traffic. See the commit 54af5a2 for suggestions of how to add other link types. In this case, the wireless management in OpenWrt will do the association of the wireless interface when it comes up. The second puts a “physical” link under the control of bat0. Options for an interface with option proto 'batadv' are described in the batctl man page, available at this time at config interface 'bat0' Here it is taken verbatim from commit 54af5a2 that introduced the 2019 configuration.Īdjust if you have a reason to do so. The first, bat0, is the “control” interface. Now that the mesh is (or could be) up and running, create the batman-adv interfaces for routing traffic over the mesh.Ĭonfigure all mesh nodes with the same two /etc/config/network stanzas:
0 Comments
Leave a Reply. |