Live data from Hacker News

40% of Google users now connect via IPv6

google.com

251–260 of 353 posts

Re: 40% of Google users now connect via IPv6

#251

Earlier quoted context omitted.

True. As an ISP you are gonna need an IPv4 stack no matter what. Even if that stack is CGNAT'd up the ass. I can't even ping news.ycombinator.com or amazon.com with IPv6. That is the biggest problem with IPv6. Who is gonna be the first ISP to shut off their IPv4 stack? There is always gonna be some random website that is IPv4.

When all the big services become IPv6, the number of IPv4 megabits will become small. You might just direct all the v4 traffic via a tunnel to another ISP which specializes in legacy services like IPv4, running SMTP/news servers, etc. Now you've saved all the cost of maintaining all the IPv4 peerings and config.

>When all the big services become IPv6, the number of IPv4 megabits will become small.

Well I have been hearing about the end of IPv4, and IP exhaustion for about 20 years now, and I fully expect people to still being moaning about it 20+ years from now while the majority of the interment still communicates over ipv4

Re: 40% of Google users now connect via IPv6

#252

Earlier quoted context omitted.

I’m on Vodafone/Kabel Deutschland. IPv4 only, my only option would be to switch to CGNAT to get IPv6, which I’d rather not.

Not sure why thats the case for you. I'm on Vodafone/Kabel Deutschland too and got full ipv4/ipv6 dual stack? Is that one of those regional limitations that Vodafone seems to have?

Oftentimes you can just ask the customer service of Vodafone. If you reach a good agent, they will switch you away from CGNAT and you get a proper /56 public routable prefix on your cable line. Also works great for me. Be aware, the Vodafone modem won‘t forward the prefix for you. Use a Fritzbox or one of the other few cable modems where you get full control.

Re: 40% of Google users now connect via IPv6

#253

Earlier quoted context omitted.

I just hope ipv6 doesn't have privacy nightmare that 1 device will always get 1 IP. Currently, the isp I use provides dynamic ip, so on every router restart my ip gets changed. If they starts to provide ipv6, I hope they give options to rotate it frequently, so toxic companies like meta, facebook, microsoft can't connect my device & ip.

IPV6 is sort of like the new MAC address hardware identifier. An IP for every atom in the universe!

There are a lot more atoms (10^80 or so) than IPv6 addresses (10^38).

How could a device have a hardware-embedded IP address, if the hardware vendor doesn't know which ISP you will use?

Re: 40% of Google users now connect via IPv6

#254

I'd be using IPv6, but it's not directly supported by Sonic Fiber in the bay area, strangely enough. Need to use 6in4 tunnelling if you want it.

I’m a Sonic customer, and have a fully working IPv6 connection from them.

How?

https://help.sonic.com/hc/en-us/articles/115000419168-Fiber-...

Gigabit fiber from them explicitly says it isn't supported.

Re: 40% of Google users now connect via IPv6

#255

Earlier quoted context omitted.

Ubiquity has several gateway products that have no hardware acceleration for IPv6. It's not a _good_ reason, Ubiquity should've included IPv6 support from the start with the price they're asking, but it's a reason.

Even worse, to this day, Ubiquity still does not support Android IPv6 clients because their internal-facing RA dnsmasq configuration has a bug. It would take an engineer a few hours to fix it; it's a one-line change. It's been reported and tracked internally in their support queue for more than two years; nothing has come of it.

It's stuff like this that's turned me away from buying Ubiquity.

Re: 40% of Google users now connect via IPv6

#256
post #184

Its mostly impossible to run servers only with IPv6 since for some reason Canonical/Ubuntu decided to require IPv4 for snap, after years of not having any issues with IPv6 only deb mirrors. Go is also basically bound to IPv4 since it depends on github to pull packages its time to make hall of shame for software that does not allow developers to build IPv6 only going forward.

Wait, GitHub still doesn't support IPv6?

Neither does DuckDuckGo. Been a feature request for >5 years now.

I'm 99% certain that they turn off IPv6 to avoid complaints. Implementing IPv6 on a frontend load balancer is a trivial networking change. But the only way to ensure an IPv6 connection works is for the user's OS, networking, firewall, router, modem, ISP backend network, ISP DNS resolver, target website DNS, and target website load balancer & firewall, all have IPv6 configured properly. If a single step is misconfigured, or uses IPv6 tunneling/translation, every request might be blocked until the website disables IPv6. So don't support IPv6 at all and you avoid headaches.

Avoiding an unnecessary support headache is the basic reason why IPv6 has existed for 26 years and yet Google can still barely get 40% use for its own website. Everybody loves to design a spaceship, but nobody designs for moving between spaceships mid-launch.

Re: 40% of Google users now connect via IPv6

#257

Earlier quoted context omitted.

You’re presenting a false dichotomy. The choice for an ISP today is not “v4 or v6”, it’s either “v4 or v4+v6”. A v6 only connection in the US is unusable.

All apps on iOS support DNS64 on ipv6 only network.

That doesn’t help for servers that are only reachable via ipv4 (see GitHub).

Re: 40% of Google users now connect via IPv6

#258
post #242

Earlier quoted context omitted.

You’re presenting a false dichotomy. The choice for an ISP today is not “v4 or v6”, it’s either “v4 or v4+v6”. A v6 only connection in the US is unusable.

The more traffic you can get onto ipv6 the less stress is on the v4 infrastructure. Each v6 connection is one your CGNAT doesn't have to provide an ipv4 port for.

So what? That’s still just a scaling factor at that point and still requires you to have v4 cgnat infrastructure + ipv6.

Re: 40% of Google users now connect via IPv6

#259

Earlier quoted context omitted.

When all the big services become IPv6, the number of IPv4 megabits will become small. You might just direct all the v4 traffic via a tunnel to another ISP which specializes in legacy services like IPv4, running SMTP/news servers, etc. Now you've saved all the cost of maintaining all the IPv4 peerings and config.

>When all the big services become IPv6, the number of IPv4 megabits will become small. Well I have been hearing about the end of IPv4, and IP exhaustion for about 20 years now, and I fully expect people to still being moaning about it 20+ years from now while the majority of the interment still communicates over ipv4

Amen. I dual stacked my home network 10 years ago. 5 years ago I joined an ISP that gave me CGNATv4 and IPv6 and I opted to disable IPv6 at the router.

Re: 40% of Google users now connect via IPv6

#260

Earlier quoted context omitted.

Yes, I understand how NAT works. But CPU/memory is going down in cost way faster than bandwidth demand is increasing. Regardless, its way way cheaper than buying IPv4 blocks clearly, otherwise people wouldn't be doing it. Edit: ok, the problem isn't hardware, it's comedy license fees. https://itprice.com/juniper-price-list/cgn.html $470k for a license to do CGNAT at 100gbit/sec. Surely these guys are opening themselv…

Software-defined networking is slowly becoming more popular, but it’s always going to be more resource intensive than these enterprise-grade routers that are typically implemented using FPGA / ASICs. Having said that, I’m often equally baffled at just how expensive modern networking hardware is, but as it’s pretty much all of these carrier grade networking solutions being this expensive, I’m assuming it’s somewhat ju…

I’m not sure the price is justified, however the ISP market is extremely difficult/impossible to break through for startups or any company capable of building their own. It’s a self-fulfilling prophecy, the market is hard to break into (for other reasons besides networking equipment cost) so nobody who can actually do something about it is able to get in.
Post reply on HN