Live data from Hacker News

Tell HN: IPv6-only still pretty much unusable

news.ycombinator.com

71–80 of 649 posts

Re: Tell HN: IPv6-only still pretty much unusable

#71

Earlier quoted context omitted.

How is a host with a 32-bit address supposed to communicate with a host with a 128-bit address when it can only send packets with a 32-bit address?

That's a solved problem whose solution is called ipv4 over ipv6 tunneling.

that will cause state and can hurt performance since it needs extra memory. one of the main selling point of IPv6 is try to be stateless as much as possible to ease up on routers and switches

Re: Tell HN: IPv6-only still pretty much unusable

#72
Yes, I use IPv6 in production, alongside IPv4 (dual-stack). I've got an IPv6 only EKS cluster that has IPv4 on the local instance that NAT's any IPv4 outgoing connections, but the entire cluster and all communications inside the cluster/between pods is IPv6 only.

IPv6 stand-alone without IPv4 dual stack is not yet an option, but it is getting closer. If you can mirror content and deploy from your mirrors it is entirely possible to do everything over IPv6 alone.

About 30% of my production traffic is IPv6, referring to outside traffic coming in to the systems. Internally almost 90% of the traffic is IPv6 due to the k8s cluster being IPv6 only, and preferring that over IPv4.

Interestingly enough at home on my home connection about 60% of my traffic is IPv6, which has been increasing steadily over the years as other companies have started bringing on-line IPv6 for their services.

Re: Tell HN: IPv6-only still pretty much unusable

#73

Having "grown up" with IPv4, I'm slow to learn everything necessary to set up an IPv6 infrastructure. The times I did look into it, IPv6 seemed so much more complicated than IPv4, but maybe that's just because I'm just not familiar with it. Are there any good resources on setting up IPv6 support from first principles? I still get confused as to the "right" way to set up internal networks for IPv6, especially when DHC…

Everything should get its IPv6 configuration via SLAAC. DHCPv6 is only useful when you plan to provide prefix delegation for extra routers or network boot information.

just a funny joke: what about using IBGP/OSPF for prefix delegation?

Re: Tell HN: IPv6-only still pretty much unusable

#74

And this is where government regulation would have helped. It's a shame nobody listened to me back in the 90's: (it's a joke. I'm a nobody, there is nobody listening.) All cell-phones should have been ipv6 from the get-go. Now if we could just go back in time and warn everybody about IPv4 address space being exhausted. And maybe the climate too while we are at it. Seriously though, cell-phone adoption would make that…

It’s not that ipv4 space is exhausted, there’s plenty of it available. It’s that early on it was mismanaged to the point that people / companies were able to buy entire /8’s for basically nothing and hold them forever.

Related anecdote, my (small) school had acquired a /16 way back and so today, every single device on the network gets its own public ipv4. It was an absolute mess for security (imagine a small army of first year CS majors setting up each a Raspberry Pi) but it was kinda fun being able to experiment with servers without having to worry about NAT.

Re: Tell HN: IPv6-only still pretty much unusable

#75
post #32

IPv6 has been one of the biggest failures in the last couple of decades. And I don't mean adoption, I mean the standard itself. If IPv6 were IPv4 with more octets, then we would all have been using it for like a decade. Yes, I understand it would still require some breaking changes, but it would have been a million times easier to upgrade, as it would be a kind of superset of IPv4 (1.2.3.4 can be referred as 0.0.0.0.…

"::ffff:1.2.3.4" is a valid IPv6 address; "IPv4-mapped IPv6"

Re: Tell HN: IPv6-only still pretty much unusable

#77
post #43

Earlier quoted context omitted.

Actually HN is available via IPv6 over Cloudflare. You have to add a CF IPv6 it to the hosts file. In fact I am posting this comment over IPv6.

> hosts file 1986 wants a word.

I actually run a separate DNS proxy that does it automatically for me. (HN and lot of other sites)

I only mentioned hosts file because it is the easiest way to spoof the domain.

Re: Tell HN: IPv6-only still pretty much unusable

#78

I was thinking about ipv6 the other day. I concluded in my head that adoption was just around 5-10%. Luckily I went to verify that with statistics. https://www.google.com/intl/en/ipv6/statistics.html While price of ipv4 addresses are increasing, the world has slowly been adopting ipv6. From the graph above, I'd say we cross over 50% in about 2-3 years time. At some point the "dash" to adopt ipv6 starts, and brave fol…

That is a very one-sided view of adoption. It ties directly with the rise of mobile and internet in areas that wasn't able to grab IPv4 addresses in time. Such as India. Not sure what France is doing though, maybe something right.

So, from my perspective (which obviously is tied to my location) is that all computers have IPv4 (haven't heard (and I've asked) of a single consumer ISP that offers IPv6) but all mobile phones have IPv6. Whether people in general do most searches on mobile or PC is gonna change that graph dramatically, but won't explain what I would be interested in regarding ipv6 adoption. That is, how much of the world would be broken without IPv4?

And for that, that graph isn't completely useless - but not too far off.

Re: Tell HN: IPv6-only still pretty much unusable

#79

I think IPv6 internal-only is viable with some kind of NAT64 setup, maybe not at scale though. What is everyone using for NAT64?

Would use OpenBSD + unbound to get NAT64 + DNS64. I'd prefer a dual-stack setup with RFC1918 IPv4 internally + a NAT44 gateway and IPv6 "just" on top. Drawback: if you find yourself to have to do a lot of firewalling it essentially doubles your work.

Re: Tell HN: IPv6-only still pretty much unusable

#80
post #53

Earlier quoted context omitted.

How is a host with a 32-bit address supposed to communicate with a host with a 128-bit address when it can only send packets with a 32-bit address?

If it's not "Ipv4+" aware, it wouldn't be able. Otherwise it would understand new packet formats.

So exactly like current situation, with content providers forever stuck at providing old version for old clients.
Post reply on HN