HN Reader

Sure ipv6 has some better features, but dual-stack means you are doubling all of your config (ACLs, naming, firewalls, routing) test cases and vulnerability surface. Moreover, ipv6 is not as intuitive.

Shaming people into ipv6 will never work. More effort should be invested into best practices, patterns, migration guides, support communities & more to assist in operating in a dual-stack environment for the foreseeable future.

Pure ipv6 will never happen because the weak link breaks the chain. How many people set up an ipv6 VPC with great excitement, and late in the project they deploy from github with "NS lookup failed".

6 months agoby tonymet

I did this for a couple days when Comcast's DNS was fucking up when I moved into a new place and was stuck with their modem/router/AP for a bit (which was locked to like 6.6.6.6 or whatever it was).

Tried explaining it to several customer support techs but they all just gave up eventually.

Was fixed when I ended up getting my own modem and router/AP.

But those were an interesting few days. My partner was annoyed they couldn't use Pinterest but YouTube loaded fine. Google search worked but our local pizza joint's site didn't.

6 months agoby kacesensitive

My networks are IPv6 only for a couple of years, but I do have to run NAT64 (jool) and use a DNS64 resolver (i use a google-provided, but you could run your own)

It had very little benefits at the beginning, but having dedicated publicly routed addresses started to become really conevinent.

IPv6 with a regulary changing dynamic prefix still sucks though to this day ... :-(

6 months agoby herczegzsolt

Google global IPv6 traffic hit the highest ever percentage 49.76% on July 26th. 50% any day now.

https://www.google.com/intl/en/ipv6/statistics.html

6 months agoby easterncalculus

Nowadays I consider IPv4 address scarcity almost a feature, because of rate limiting and DDoS mitigation in general.

6 months agoby redox99

Thread was pretty much a greenfield deployment at the time, so it use of IPv6 was easy to specify. There was now legacy IPv4 to support or otherwise it would probably be a mess as well.

6 months agoby sybercecurity

‘Considering the pool of available IPv4 addresses has been exhausted for quite a while now, and was running out for public use years ago’ I thought it was logical that most systems that have adopted IPv6. Crazy to think that it turns out it wasn’t, but shout out to apple and their stringent dev requirements bc they require support IPv6-only networks.

6 months agoby evaXhill

What are the advantages of IPv6 if I don't want direct routing (NAT is a feature for me, not a workaround)?

6 months agoby ghusto

Out of curiosity, I had a look at one of our service's login nodes, to see where SSH connections were originating from off-campus. What I found was that approximately 30% were over IPv6.

Anecdotally, during weekday working hours, the percentage of IPv6 is higher than (typically over 50%).

6 months agoby CaliforniaKarl

turning off IPv4 ... was harder than I expected it would be

This is followed by reasonable reasons they struggled to unwind themselves from IPv4 (for the experiment) - but eventually got it worked out.

Conversely: When I hotspot from my phone, T-Mobile frequently makes that an IPv6-only experience.

6 months agoby WarOnPrivacy

I recently switched ISP to one that supports IPv6 and I have had nothing but problems. I have had DNS servers going missing from OpenDNS, I have seen all sorts of really weird routing errors and transient problems, its barely usable at all. Linux seems to be more strict about how it handles IPv6 and I found my server couldn't find its upgrade packages because some of their mirrors are broken for IPv6 routing. All in all it was a mess and I turned it off. My ISP must be partially at fault but it was clear Debian was too as was OpenDNS and most of my problems no one could explain what was happening or why.

6 months agoby PaulKeeble

When an ISP assigns an IPv6 prefix, home networks / homelabs can use that prefix for internal addressing. But if the ISP later changes the prefix, all internal devices using the old addresses break. This makes the concept of globally unique IPv6 addresses seem problematic for end-users. Is there something I’m misunderstanding about how this is supposed to work?

6 months agoby waynesonfire

I recently decided that it was high time to stop ignoring IPv6 after 30 years of computing and actually learn how it is supposed to work.

So I started digging in, and there's definitely a lot to like.

But I see two big problems that are showstoppers in my opinion, at least for my home network (not even considering the fact that very few residential ISPs even support v6 at this point):

1. Generally speaking, the IPs of your LAN are based on the prefix assigned by the ISP. Most residential ISPs don't offer static prefixes. This means that every time your prefix changes, the IPs of all your devices on your LAN change. Seems like this "feature" was developed in a more idealistic era when people probably thought everyone would be getting static IPv6 addresses, since shortages would never be an issue. Unfortuantely, they failed to foresee the fact that most major ISPs are terrible, greedy organizations that either outright refuse to offer static assignments, or continue treating them as if they were scarce IPv4 resources, charging a premium or requiring business-class service to even get them.

2. The ISPs that do support v6, like Comcast/Xfinity in the USA, are only allocating one /64 prefix. This means you can only have one subnet (VLAN) on your LAN! Why are they being so stingy?

I would love to migrate to IPv6, but these two issues alone make it feel like a clown show for home users.

6 months agoby dogcow

I feel like a more interesting question is what proportion of users can connect to an IPv6-only server?

6 months agoby IshKebab

When I bought a new gaming PC recently it default configured on my home network with IPv6 but not IPv4. It was interesting which features Microsoft considers crucial (and so worked on IPv6) and which were not important (and so they just didn't function, claiming that there's no Internet even though of course there is and e.g Google works)

Advertising for example, was essential. Spewing garbage I don't want, absolutely critical to Microsoft's bottom line apparently. But registration so that I can turn off that advertising? Not important, so that was not available until I gave the machine IPv4.

6 months agoby tialaramex

When PlayStation and Nintendo support ipv6 only then you may see consumers care.

6 months agoby ectospheno

My ISP still only gives 6rd..

6 months agoby mistyvales

Work is exclusively IPv4 and nobody's talking about changing. Everything at home is IPv4 and I'm not even curious about IPv6. When I have to be, I'll figure it out. Until then, things seem to be working fine.

6 months agoby SoftTalker

Maybe it's me, but I think IPv6 should have been 8 bytes instead of 16 and somewhat backward compatible with IPv4.

Like how 2-byte Unicode was struggling and UTF-8 saved it.

6 months agoby habibur