3 ms·
This is one of the worst takes I've seen in this thread. NAT is only kind of a firewall and there have been plenty of terrible router firmwares out there that
by pixl97 4y ago
This is one of the worst takes I've seen in this thread.
NAT is only kind of a firewall and there have been plenty of terrible router firmwares out there that have lead people to subvert it (UPNP being one of the most problematic).
If you in your other thread don't trust the ISP device, then don't trust NAT on your ISP device either. Quite often the ISP can have their modem route traffic from their internal 10 net to your internal network if they so choose to.
Instead IPv4, or IPv6 setup to drop NEW/SYN connections to your devices via a router that you provide.
- phpisthebest 4y ago>If you in your other thread don't trust the ISP device, then don't trust NAT on your ISP device either There is no logic there. firewall configuration is much harder to secure than NAT configuration.
- lmm 4y ago> There is no logic there. firewall configuration is much harder to secure than NAT configuration. Disagree. Just the XML parsing logic required for uPnP alone is more complex than a basic firewall implementation.
- JohnFen 4y agouPnP seems a distraction from the topic. It's not necessary for networking to network -- my LAN intentionally does not support it at all. It is necessary for certain use cases, of course, but it's not mandatory in a network in the general case.
- lmm 4y agoIt's necessary for feature parity with IPv6 (or, equivalently, with the 2000s-era Internet). Even if you don't use uPnP, the amount of complex protocol parsing necessary to support/work around NAT (e.g. SIP is particularly tricky) is a larger attack surface than a full IPv6 stack.