and here comes the new device: AP1200b that should connect with mesh backbone on 2.4Ghz to AX6000 and extend the network. (on Router7530 and AP1200a I deactivated the mesh part again, left it for the future)
also it should serve the VLANs that I am about to utilize for Guests and IoT
i am new to OpenWRT, love it already and think I came a long way by following tutorials and learning. but now I hit a wall.
what I need is to be able to plug the AP1200b into the power and from there being it connect to AX6000 through the backbone 2.4Ghz mesh where batman is waiting to serve VLANs and make everything fine.
i have a bridge device called "Switch" that has Switch.01 lan Switch.20 Guest and Switch.30 IoT
please let me know where my mistake is, as soon as I disconnect and replug the AP1200b I don't get access to Luci because no IP is communicated through VLAN to Router and back with DHCP
bat0 should not be on your bridge. Instead you need to create a new bat0.1 untagged to vlan1. Do the same to bat0.20 and bat0.30 all untagged to their respective vlans.
Batman mesh communication is handled by the interface using the batadv_hardif protocol...not bat0 itself.
If you want batman to take over your entire network then yes...you can add it to every device and just let batman manage your routing but I would not see the benefit of this if you only have a single internet connection. However, if you have multiple internet connections then yes I would configure all my access points with batman and let batman sort out the routing.
one last thing is to check your syslog for errors related to packets sent and received on the same interface. This is a mac address related issue. The latest openwrt 23.05 completely solves this by allowing you to set random mac addresses. Prior to this version you will need to manually set unique mac addresses.
My Situation: Router7530 with DSL AP1200a eth backbone to Router AX6000 eth backbone to Router AND batman mesh to AP1200b (2.4Ghz) AP1200b mesh backbone to AX6000 (2.4Ghz)
Can you point me to that tutorial. I don’t mess around with this on a daily basis so there is chance something’s different now.
But generally mesh is already a virtual switch by design, so no need to make a switch within a switch. You don’t need to create a «managed switch» since the vlan-like functionality is already built-in in batman.
Just bridge the respective bat0.x to the bridge associated with the respective interfaces and batman takes care of the rest.
I don't think that tutorial covers the mesh part. Wifi doesn't directly support vlan so that's why batman has it's own vlan functionality which basically works just the same just that bat0 is already the virtual trunk so you don't need to "create a virtual managed switch"
@anon27495695 you are correct...batmanadv is a L2 protocol that be used to extend a VLAN network over wireless communications. It's just one of its functions among others. The DSA bridge is there to manage the VLAN filtering.
