Hi,

I have found a small bug in the AX3000 router. I have a internal network (with a different IP space than the router) under the LAN of the router. There is also a different router between this network and the TP-Link router. So something like this:

PC (10.10.10.5) --------- (10.10.10.1) ROUTER (192.168.0.100) -------------- (192.168.0.1) AX53 ROUTER (DHCP) ------------ INTERNET

After adding a static route to this 10.10.10.0/24 Lan to the AX router, I'm able to ping the AX53 router from the PC, BUT by default I can't ping or connect to the "outside world" from the PC.

I can make it work if:

a) I maintain the same ping command open (ping -t in Windows) and...

b) Switch the "Respond to pings from WAN" on or off.

Switching that setting seems to flush the conntrack table (according to the log) and the pings go throught temporaly. If I interrupt the ping and start it again it doesn't work until I switch again the "Respond to pings from WAN" setting.

I have tried to set the SPI Firewall off without results.

I'm sure this is not a common set up for this kind of router but I think it is clearly a bug nonetheless.

It would be nice to get this solved in a firmware update. We own 20 of these devices :)