I've been using OpenWrt for a couple of years now and overall everything is running extremely smooth. For the past couple of days I'm trying to add a new network, similar to the default
lan that will house specific devices that need to be seperate and invisible from the rest of the network. Those devices are both wired and wireless. Here's a picture of my current setup:
As you can see the network consists of 3 devices, an ISP-provided modem/router in bridge mode and two OpenWrt-flashed ASUS RT-AC58U routers, which have been upgraded to OpenWrt 21.02.0-rc2 as part of this test. The first of them connects through its WAN port to the ISP's modem/router LAN1 port and does PPPoE. The second one connects to the first one, again through its WAN to the first's LAN1 port and get a DHCP-provided IP address.
The second one has everything router-related disabled and its WAN port bridged to the LAN through LuCI. It is assigned a statically assigned DHCP address (192.168.1.2 for the record) from the first router. Both devices have the same WiFi networks in both 2.4GHz and 5GHz for roaming. This setup is proven working and has served multiple devices for the past months.
Jumping to the past couple of days and my new requirement. I have created a new Firewall zone, a new Interface and new WiFi access points on the first router and I can confirm that everything works. I'm getting an IP from a different subnet (which is what I want), and devices from lan can't reach devices in my new network. I have also setup VLANs on both sides and I can get connectivity on both ends (e.g. I can get an IP from my new network on the second router's switch). I can connect to the new SSIDs and a specific LAN port and be inside my new network.
There are two issues that I'm facing (which could be related):
I'm getting a lot of
Sat Jun 12 16:09:17 2021 kern.warn kernel: [ 309.102915] br-lan: received packet on eth0.10 with own address as source address (addr:04:92:26:xx:xx:xx, vlan:0) on the first device's System log. I understand that the two bridges have the same Mac address, but I'm not sure why that happens since they are on different VLANs. I'm also getting the same message for eth0.20, my other network.
Some wired devices on the first router seem to not be able to get an IP address. I can see in the logs that some of the get stuck in a loop between DHCPDISCOVER and DHCPOFFER and never actually getting an IP (the router seems to offer one though).