Re:IPv6 is not insecure because it lacks a NAT
by everdrive on Wednesday January 21, 2026 @06:25AM
(#46704084)
Right, IPv6 is annoying because it lacks NAT. There's a big difference between something being a huge pain to deal with (IPv6) and being insecure.
[ Parent
| on HN ]
Re:IPv6 is not insecure because it lacks a NAT
by rnhmjoj on Wednesday January 21, 2026 @06:54AM
(#46704397)
Ok, I'll bite: why do you say that IPv6 lacking NAT (which is not true by the way) would be annoying? We can finally get rid of an ugly workaround from 30 years ago that broke one core principle of the Internet (end-to-end connectivity) and a ton of protocols that required even uglier hacks (FTP and SIP ALGs, TURN/STUN, etc.) to barely work. Why would this be annoying?
Re:IPv6 is not insecure because it lacks a NAT
by InfamousRece on Wednesday January 21, 2026 @02:17PM
(#46710158)
At my previous place IPv6 was useable (I was getting /60 prefix rather than /64 Iām getting now) but the prefix was changing often - several times per day. This was annoying because every prefix change all addresses of my devices changed too. So in practice I always used private IPv4 addresses to connect to them.
A NAT would solve this issue.
Re:IPv6 is not insecure because it lacks a NAT
by rnhmjoj on Wednesday January 21, 2026 @03:33PM
(#46711155)
Well, delegated IPv6 prefixes are supposed[1] to be static or somewhat persistent, but some ISPs do this, yes. This is most likely a practice carried over from IPv4 where there is a small pool of addresses. Fortunately in my experience it's not too common: most ISPs that deployed IPv6 did it the right way.
Anyway, to get persistent addresses you can set up a ULA prefix (the equivalent of RFC 1918 addresses) and a simple prefix translation[3]. This is a form of NAT, but unlike the usual IPv4 NAT (actually NAPT) it doesn't deal with ports, so it's slightly less annoying problematic. There also are a few more techniques, like using mDNS and writing firewall rules that match the suffix of the client addresses, but not many CPE allows for this.
[1]: https://www.ripe.net/publications/docs/ripe-690/#53-why-pers...
[2]: https://en.wikipedia.org/wiki/Unique_local_address
[3]: https://openwrt.org/docs/guide-user/network/ipv6/ipv6.nat6
Re:IPv6 is not insecure because it lacks a NAT
by Dagger2 on Thursday January 22, 2026 @09:50PM
(#46727754)
You don't need prefix translation to use a ULA prefix. You just configure both the ULA and the ISP-delegated GUA prefixes simultaneously.
Re:IPv6 is not insecure because it lacks a NAT
by rnhmjoj on Friday January 23, 2026 @10:47AM
(#46733876)
Right, the ULA prefix theoretically has lower preference, so it should only be selected to reach hosts in the LAN and the GUA for everything else, but I don't know how well softwares handle this in practice.
Re:IPv6 is not insecure because it lacks a NAT
by Dagger2 on Sunday January 25, 2026 @12:21AM
(#46751001)
Source address selection is usually left to the kernel, so that part should be okay. It'll pick a GUA source for a GUA destination unless you've changed the labels with `ip addrlabel`.
Re:IPv6 is not insecure because it lacks a NAT
by craftkiller on Wednesday January 21, 2026 @06:56AM
(#46704413)
IPv6 doesn't "lack" NAT. There is nothing preventing you from using ULA addresses inside your network (IPv6's version of RFC-1918) and then running NAT for those addresses on your router. IPv6 just doesn't _need_ NAT, but it is still an option.