how is localhost still reaching domains without localhost NAT rules?
-
At some point during the configuration of my firewall I deleted my localhost NAT rules in advanced NAT. I am clueless as to how my firewall is still able to download package lists and check for updates. I have reset states and rebooted with this configuration and it is all still working. How is this possible when localhost 127.0.0.0/8 no-longer has NAT configured to any gateway destinations? I understand this isn't a problem as such but I'm just trying to understand how this is still working.
-
Most often those things are sourced from an interface address, not localhost. The localhost NAT rules allow things which specifically choose to bind to localhost to route out. That is not typical, but still expected to work.
-
@jimp Thanks, that makes sense. So what things would you expect to bind strictly just to localhost? I have since reconfigured my localhost NAT rules but nothing seemed to break without those rules in place.
-
Not much out of the box, but some people choose to bind daemons like OpenVPN, ntpd, or the DNS Resolver to localhost for a variety of reasons.
-
Ah yes, I do remember reading about binding to localhost for dual WAN setups. Thanks for the info, it's great to have such a knowledgeable and helpfull community.
-
@jimp Ah yes, I do remember reading about binding to localhost for dual WAN OpenVPN setups. Thanks for the info, it's great to have such a knowledgeable and helpfull community.
