6 ms·
> This is completly incorrect. While NAT is almost always combined with a stateful firewall, the NAT itself does not provide any security. It most certainly do
by jedberg 7y ago
> This is completly incorrect. While NAT is almost always combined with a stateful firewall, the NAT itself does not provide any security.
It most certainly does. If you have an insecure device behind a nat, say something with telnet sitting open, a port scanner from the outside won't be able to find it (unless you've gone to great efforts to allow inbound connections without an established outbound connection). This is objectively better than if that device were directly addressable.
> Home devices are always going to be deployed with an allow outgoing, deny incoming firewall, regardless if they have IPv6 or not.
Not always. My last router came with the firewall off and that was just a few years ago. A lot of consumer ISPs don't bother with the firewall because they don't want to field customer service calls about things not working.
- lostlogin 7y ago> A lot of consumer ISPs don't bother with the firewall because they don't want to field customer service calls about things not working. This is amazing. How does it work? What stops me going to the devices behind the router?
- zAy0LfpBZLC8mAC 7y ago> It most certainly does. No, it doesn't. It's a commonly believed myth among people who don't have a clue how IP works, though. > If you have an insecure device behind a nat, say something with telnet sitting open, a port scanner from the outside won't be able to find it Why not?
- icedchai 7y agoWhen most people say "NAT", they really mean "PAT". Port address translation: multiple private IP addresses behind a single public IP address. When a non-pedantic person sees "NAT", they understand it is actually "PAT." And in the typical consumer configuration, it actually does provide some level of security.
- Dagger2 7y agoAnd when people talk about "PAT", they're actually talking about a form of NAT that doesn't block connections. Here's how you do "PAT" on Linux: `iptables -t nat -A POSTROUTING -o wan0 -j MASQUERADE`. Notice how it's limited to outbound connections ("-o wan0")? That means it doesn't apply to inbound connections, and thus doesn't have any effect on the behavior of inbound connections. If it doesn't have any effect on the behavior of inbound connections, then how could it possibly block inbound connections? (The typical consumer configuration pairs "PAT" with a firewall, and the firewall does block inbound connections. It's also typical to pair it with RFC1918 addresses, which doesn't block connections but does make it much harder for most people to make the relevant connections in the first place. None of that changes the fact that "PAT" doesn't block connections.)
- icedchai 7y agoSo in other words, even without a firewall, it still provides some level of security. If your attacker can't route to your target's addresses because they are private RFC1918, they're "blocked" for all practical purposes. Yes, I know they're not technically blocked... but the typical attacker 10 hops away isn't going to know...
- zAy0LfpBZLC8mAC 7y agoOn the other hand, this might also give other people a false sense of security. Most people who tell you that "NAT provides security" think that NAT somehow drops packets, and if your network is actually targeted, this myth might well be the reason why someone ends up downloading all your files by connecting to your file server through your NAT gateway.