2 ms·
> NAT and hide all these devices behind a single external IP. If/when I'm forced to shift my LAN to IPv6, this is the approach I'll take. I don't want any rand
by JohnFen 3y ago
> NAT and hide all these devices behind a single external IP.
If/when I'm forced to shift my LAN to IPv6, this is the approach I'll take. I don't want any random machines behind my router to be able to open ports to the internet at large. I want a single point of presence that handles that and forwards to whichever machine I want to handle that traffic.
For those who are excited about IPv6, I hear you and your use cases are legit. I just don't share them and want the most restrictive network setup that I can tolerate.
- noinsight 3y ago> I don't want any random machines behind my router to be able to open ports to the internet at large. The solution to this is a firewall, not NAT. As has always been. NAT is not a security feature and never has been. The fact that it blocks uninitiated inbound connectivity is an implementation detail, not its purpose.
- JohnFen 3y ago> NAT is not a security feature and never has been. True, and I don't think of it as such -- after all, NAT or not, it's my firewall doing the protecting. What NAT would buy me here is convenience, not security. I could have the same level of security without NAT, but managing it properly is easier and less error-prone with it.
- kstrauser 3y agoHaving managed both, it is absolutely, 100%, not easier to manage NAT than a firewall. For example, here's a valid OpenBSD pf configuration: pass out on $ext_if from any to any That's it. That's the entire stateful firewall config: Don't allow anything inbound at all, except directly in response to an outbound connection. If your firewall has a GUI, it'll be as easy to configure that as it is the NAT. If your firewall has a CLI, I guarantee there's no NAT in the world that's easier to configure than the above stateful firewall.
- JohnFen 3y agoWell, it's not quite that simple given my LAN's topology -- but you're right that it isn't incredibly complicated. I just prefer to manage it a different way. The end result is the same, so I'm not sure what the issue is here.
- ranger_danger 3y agoDepending on your threat level and exact firewall configuration, any bidirectional connection can be used to punch through in some way.
- kiririn 3y agoFirewalls don’t fail safe, NAT does. With a disabled/broken/misconfigured firewall, there is a good chance that everything works sans security. With a disabled/broken/misconfigured NAT, you may as well have unplugged the ethernet cable
- p_l 3y agoOr allowed one of the many NAT-busting methods to connect through.
- Dagger2 3y agoIt doesn't even do that much. NAT is something you apply to outbound connections, not to inbound ones. Unless there's a firewall blocking it, you can connect inwards over a router that's NATing its outbound connections.
- Arnavion 3y agoSince every IPv6 discussion on HN has to repeat this misunderstanding, I'll just link to what I posted last time: https://news.ycombinator.com/item?id=39997078 https://news.ycombinator.com/item?id=39997078
- JohnFen 3y agoWhat misunderstanding? I am familiar with what you wrote, and am not disagreeing. There is nuance here that seems to get lost whenever this topic comes up.
- Arnavion 3y agoThe misunderstanding that "I don't want any random machines behind my router to be able to open ports to the internet at large. I want a single point of presence that handles that and forwards to whichever machine I want to handle that traffic." is something that happens with v4 and not with v6, or that it has anything at all to do with NAT.
- JohnFen 3y agoI wasn't suffering under that misunderstanding. I was just saying what my personal preference is for managing such a setup.
- kstrauser 3y ago> I don't want any random machines behind my router to be able to open ports to the internet at large. While it's hypothetically possible to have NAT without a firewall, I've never personally touched or seen such a thing. I can confidently state that if you have NAT, you also have a firewall. Use it.
- JohnFen 3y agoI never said a thing about not using a firewall. My firewall is what protects my LAN, after all.
- kstrauser 3y agoThen you’re not getting any extra protection from a NAT.
- JohnFen 3y agoTrue! I wasn't claiming that I was. What I am claiming is that doing it this way is more convenient for me. Since IPv6 doesn't give any benefits that matter to me, the only reason I'd do it is to maintain the ability to talk to my ISP. So my goal would be to make the transition as quick and easy for me as possible.
- jeroenhd 3y agoBecause of NAT ALGs, most consumer NAT devices actually allow plaintext protocols to bypass the internet-facing firewalls inside routers. Unless you program your own ALGs, you basically get to pick between "SIP, FTP, and a bunch of other protocols don't work without port forwards" or "your public firewall is off for almost anyone who can make your computer load an ad". NAT breaks internet protocols and as a result we got firewall-evading workarounds.
- deleted 3y ago[deleted]
- nijave 3y ago
- Dagger2 3y agoNAT is actually less restrictive for inbound connections, because it allows people to connect with just the correct port and not the correct IP+port. Instead of needing to provide the correct 80-bit number to connect, they only need the correct 16-bit number, which is small enough to brute-force. NAT doesn't even stop machines opening ports; it's your firewall doing that. It's not NAT giving you a single point of presence, that's your router. It doesn't normally restrict outbound connections either, so what's the point? All it's doing is presenting your servers in a way that makes them easier to find. NAT doesn't do any of the things you've claimed to need it for.
- deleted 3y ago[deleted]