I tested from outside and the firewall rules do block access. I've been
scratching my head for a long time now on how to solve the problem where my
employer's VPN takes over DNS. Complaints to our IT team did no good. But
now I have a work-around.
David
On Wed, Jul 20, 2022 at 11:59 AM Lonnie
Hi David,
Interesting ... yes, as you suggested, setting the NAT EXT->LAN "Source" rule
to only the local LAN(s) (ex. 192.168.1.0/24) should be what you need to limit
"loopback" to only local IPs for a particular NATed port.
Can't say I ever needed that, but should work.
Best to test hitting y
Is it possible to configure NAT Loopback on its own... ie, without opening
NAT->LAN for all sources?
I have a problem where my employer's VPN is hijacking DNS so name
resolution for my internal hosts is always getting routed to the VPN's
supplied DNS which will not resolve to my internal IP addres
