Routing two br-lan interfaces

[OskarM]

Hi!
On my RUTX50 I have WIFI STA on lan connected to another (main) AP and getting IP using relayd, the lan has static 192.168.1.2 address is bridged to eth0. In case there is no main AP, I want to access the router with AP and get IP from 192.168.2.1. I have created lan1 on 192.168.2.1, enabled DHCP in 2.0 subent and did not bridge it to any interface. I just want to route 192.168.2.0 and 192.168.1.0 traffic, so that I can have access to devices on 1.0 subnet when I connect to AP on 2.0 subnet.

Now I can connect to AP and I get IP from 2.0 subnet, but can’t ping 1.0 subnet, even the 192.168.1.2 interface.

ip routes:
192.168.1.0/24 dev br-lan proto static scope link src 192.168.1.2 metric 1
192.168.2.0/24 dev br-ifLan1 proto static scope link src 192.168.2.1 metric 10

I tried to add static routes, but that really doesn’t change anything:
192.168.1.0/24 via 192.168.1.2 dev br-lan proto static metric 1
192.168.2.0/24 via 192.168.2.1 dev br-ifLan1 proto static metric 10

I don’t want to attach AP to lan, since there is no DHCP if the main router is off. Lan and lan1 are in the same firewall zone, so there should be no issue with blocked traffic…

the metric 10 is just to make sure devices on 1.0 will use its route if it is connected.

How can I achieve this routing?

thanks

[Martynas]

Hello,

Apologies for a delayed response. Could you confirm whether the configuration issue still persists?

If so, could you provide screenshots showing where the configuration changes were made? From what you described, your setup should work as expected when the main AP is down. When a client connects to the AP 192.168.2.0/24 lan2 network, it should be able to reach the lan 192.168.1.0/24 network when main AP (bridge) is down.

Your configuration steps seem correct:

• Relayd setup: bridged lan with your main AP network;

• DHCP disabled on lan (192.168.1.2/24);

• Separate lan2 (192.168.2.1/24) with DHCP enabled;

• Bridge interfaces disabled and no interface selected in lan2 physical settings;

• AP (secondary) assigned to lan2.

• Masquerading enabled on lan/lan2 firewall zone.

If the issue persists, could you share more details about your setup or a topology of how the setup should function?

Best regards,