Why No IPv6? | Hacker News Reader

Why No IPv6?

whynoipv6.com

39 pointsmmwelt15 comments

Easy - it sucks!

I tried to failover wan on a biz network. With ipv4 NAT this just works. Local traffic doesn’t even blip. IPv6 is comically bad here. All the autoconfig magic falls on its face. I don’t want rotating ipv6 addresses everywhere. Things like nptv6 as a workaround badly supported. NAT66 etc results in comically large internal address space - the list goes on. Can we do ipv5? Ohh, and my isps won’t give out static ipv6 blocks to save address space but a static ipv4 block is easy.

you can disable privacy extensions if you don't want "rotating ipv6 addresses everywhere"

In a fail over situation, such as a small biz scenario with multiple providers, but no BGP, you'll have to deal with rotating prefixes. One alternative would be to NAT to the other provider prefix's during fail over (actually NPt: network prefix translation.) Depending on your firewall / router this may be easier said than done.

Right. NPT is not well supported. NAT66 is out there, but when you think of address space size is totally ridiculous. That said it does solve a bunch of issues.

That's disappointing. The title's "Why No IPv6?", the domain is "whynoipv6.com", the first (and largest) header is "Why No IPv6?", but I'm yet to find an answer to that question. So - Why No IPv6?

Half of the website is obscured by the sidebar

Because until it's actually a de facto standard that most sites use, it's just a PITA with no payoff or benefit.

The day I care about IPv6 is the day something breaks because I didn't support it. That day is a long way off.

Users with IPv6 will usually find a small speed increase, a few milliseconds faster for new connections. The difference is greater if the user's ISP has an overloaded CGNAT router.

Not true, in a failover wan scenario new RAs can mess a ton of stuff up on the local network and are not immediate as the local network renumbers and if routes are flapping a total nightmare. Layer in bad ipv6 routing or handling causing timeouts and fallback to ipv4

I dipped my toes into IPv6 a while back and found it pretty... disappointing? My prior understanding was that IPv6 would enable us all to get static IPs (due to there being more than enough for everyone), but it seems that turned out to be a bad idea for privacy reasons. So my IPv6 block kept changing.

Then it was a mess locally as well, where addresses kept changing and having Android units forcing you to use SLAAC because they refuse to support DHCPv6. I don't remember all the details but my take in the end was basically IPv6 not being worth the hassle.

Based on your description it appears you attempted to deploy "ipv4 with longer addresses" and got frustrated that this is not at all what ipv6 is. If you were to attempt honestly to deploy the actual ipv6 stack that exists, though not perfect, it would be a better experience.

> Based on your description it appears you attempted to deploy "ipv4 with longer addresses"

Because I honestly think this is what we (99.9999% of people) really need. IPv6 is second system syndrome. Things can fail in a thousand different ways and it's a pita to debug. Look no further than the "easy it sucks" top comment. I've had so many random bullshit problems in both, Enterprise environments and with home setups. Buggy SLAAC, buggy DHCPv6, buggy PD, just hot garbage everywhere. Prefix changing at home during the day? -> some devices work, some devices not picking up the new prefix for a couple minutes, some do but still try to use the old address. I don't care where the bug is, which device is at fault - IPv6 has been around for ages now and we still have to deal with this kind of crap. Wouldn't have happened with "IPv4 but longer addresses" and good old NAT. Google is boycotting DHCPv6, for which reason my current workplace simply disabled IPv6 for wifi, because they insist telling the device what address it gets. It seems IPv6 was created for engineers to jack off to, being actually used was just an afterthought.

Because neither my fixed line or mobile ISP support it and have no plans to. It's not something that customers are asking for. I remember trying to use the HE Tunnelbroker but then quite a few things broke on the network.

IPv6 is a PIA, it should die and govts, universities, etc. should stop hoarding the IPv4 that they have, for example the DoD literally has 74 MILLION IPv4 addresses which they are hoarding.

IPv6 has been around for over 2 decades. It is now older than IPv4 was when it went "mainstream" in the 90's, yet uptake is still quite slow. I remember, about 10 years ago, thinking the 2010's was going to be the decade that IPv6 took off. How wrong I was...

Reply on news.ycombinator.com