Dear All,
,I am having a routing issue with the WireGuard server on my GT-AX6000 running the latest Merlin firmware (3006.102.5).The client connects successfully (handshake is complete), but there is no access to the LAN or the WAN.Troubleshooting steps taken:- "Intranet Access" is set to ON. Toggling this setting off and on does not help.- As a test, I have completely disabled AiProtection, Parental Controls, and all other firewall filters, then rebooted the router. The problem persists.- The kernel IP forwarding is enabled (`cat /proc/sys/net/ipv4/ip_forward` returns 1).- The client-side firewall was also temporarily disabled for testing, with no change.- The `iptables -L FORWARD -v` output confirms that the necessary ACCEPT rule between the WireGuard interface (e.g., wg21) and the LAN bridge (br0) is missing.This seems to be a firmware bug where the "Intranet Access" toggle does not create the required firewall rules. Any help would be appreciated. Thank you.
,I am having a routing issue with the WireGuard server on my GT-AX6000 running the latest Merlin firmware (3006.102.5).The client connects successfully (handshake is complete), but there is no access to the LAN or the WAN.Troubleshooting steps taken:- "Intranet Access" is set to ON. Toggling this setting off and on does not help.- As a test, I have completely disabled AiProtection, Parental Controls, and all other firewall filters, then rebooted the router. The problem persists.- The kernel IP forwarding is enabled (`cat /proc/sys/net/ipv4/ip_forward` returns 1).- The client-side firewall was also temporarily disabled for testing, with no change.- The `iptables -L FORWARD -v` output confirms that the necessary ACCEPT rule between the WireGuard interface (e.g., wg21) and the LAN bridge (br0) is missing.This seems to be a firmware bug where the "Intranet Access" toggle does not create the required firewall rules. Any help would be appreciated. Thank you.