Hi everyone,
I'm running an ASUS AXE16000 with Merlin firmware and have several VLANs set up at home. One of them is VLAN 52, which I use with Guest Network Pro for a dedicated WiFi network for the kids.
Everything works fine when I connect the router to my switch (a Cisco SG300-28) using a standard single Ethernet cable. The SSID is active, VLAN 52 is correctly configured, DHCP is working, devices get IPs, no issues.
However, the problem starts when I enable LACP on the ASUS (eth1 + eth2) and set up a port-channel on the switch. The bond interface (bond0) is created, and I can see bond0.52 and the br52 bridge still intact, but:
Has anyone seen this behavior before? Could it be something with how dnsmasq or the network stack in Merlin handles VLANs over bonded interfaces?
Any ideas or suggestions are welcome!
Thanks in advance.
I'm running an ASUS AXE16000 with Merlin firmware and have several VLANs set up at home. One of them is VLAN 52, which I use with Guest Network Pro for a dedicated WiFi network for the kids.
Everything works fine when I connect the router to my switch (a Cisco SG300-28) using a standard single Ethernet cable. The SSID is active, VLAN 52 is correctly configured, DHCP is working, devices get IPs, no issues.
However, the problem starts when I enable LACP on the ASUS (eth1 + eth2) and set up a port-channel on the switch. The bond interface (bond0) is created, and I can see bond0.52 and the br52 bridge still intact, but:
I've verified that bond0.52 is part of the correct bridge, the VLAN is tagged properly on the switch, there's no ingress filtering, and everything works again the moment I disable LACP and go back to a single link.DHCP on VLAN 52 stops working.
Devices can join the WiFi network, but they never get an IP.
Has anyone seen this behavior before? Could it be something with how dnsmasq or the network stack in Merlin handles VLANs over bonded interfaces?
Any ideas or suggestions are welcome!
Thanks in advance.