I am seeing some strange behavior with respect to NAT loopback and wired vs wireless clients.
It appears that the default behavior is that NAT loopback is enabled on port forwarding rules. I verified this by checking the advanced settings (LuCI) interface.
Wireless clients seem to be able to reach an internal reverse proxy pointed to by a dns name that resolves to my WAN IP. (To me this indicates that NAT loopback is working to some degree.)
Wired clients do not have the same success.
I have discovered a workaround while attempting to troubleshoot the issue. If I connect to the router via SSH and run
tcpdump; wired clients can now resolve the name correctly.
How do I go about resolving this issue so I no longer need to manually intervene for packets to route correctly on and off my LAN?
It also seems very strange that
tcpdump would affect routing in this way. Has anyone seen that sort of thing happen before? I have been under the impression that
tcpdump was passive.