Batman 2nd dumb AP behind 1st dumb AP

Hi!
I set up a Batman Mesh, because I initially was planning to use a mix of wired and wireless backhaul.

However, I would like to only use wired backhaul and kept Batman. Everything works fine with a primary router and one dumb AP. I configured 3 VLANs for private use, guests and VPN.

Now I want to attach another dumb AP with a wire to the first AP. The topology looks like this:

[Main Router] bat0, batdevice on LAN4
|
(wire LAN4-LAN4)
|
[AP1] bat0, batdevice on LAN4 and another batdevice on LAN1
|
(wire LAN1-LAN4)
|
[ AP2 ] bat0, batdevice on LAN 4

For ease of use I copied all settings from the first AP, only changed the IP on LAN and names of WLAN (for testing reasons).

This works fine for both guests and VPN (only wireless, unmanaged devices). However, I can’t get internet access through the private WLAN.

Any ideas why only the LAN bridge does not work?

Network config:


config globals 'globals'
	option ula_prefix 'fd50:a449:9e6b::/48'
	option packet_steering '2'
	option steering_flows '128'

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'bat0.99'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'
	list ports 'lan4'

config device
	option name 'br-guest'
	option type 'bridge'
	option bridge_empty '1'
	list ports 'bat0.3'

config device
	option name 'br-vpn'
	option type 'bridge'
	option bridge_empty '1'
	list ports 'bat0.4'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '192.168.1.4'
	option netmask '255.255.255.0'
	option ip6assign '60'
	option gateway '192.168.1.1'
	list dns '192.168.1.1'

config interface 'guest_int'
	option proto 'none'
	option device 'br-guest'

config interface 'vpn_int'
	option proto 'none'
	option device 'br-vpn'

config interface 'bat0'
	option proto 'batadv'
	option routing_algo 'BATMAN_V'
	option bridge_loop_avoidance '1'
	option gw_mode 'client'
	option hop_penalty '30'

config interface 'batwire'
	option proto 'batadv_hardif'
	option master 'bat0'
	option device 'lan4'


Start by getting rid of Batman as it is not needed and will only be complicating things.

If these are genuine "dumb ap" configs, then daisy chaining like this should be just fine.
You only need Batman (or something else to form a tunnel) if you want vlans to propagate over a wireless link.

1 Like

Thanks! Problem solved itsself by waiting, still strange that it took such long time. As I maybe will add wireless Mesh later on, I’ll stick with Batman for now.

Why? It is not doing anything useful...

1 Like

It works.

It is easy to add a wireless AP.

But you don't need Batman for that.... It will just be adding an overhead and slowing things down, but if you are happy with it.....

1 Like

@bluewavenet is right. Batman applies to mesh network. You are using simple APs. Keep your config the lightest possible.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.