Live data from Hacker News

Google Hits 50% IPv6

blog.apnic.net

21–30 of 496 posts

Re: Google Hits 50% IPv6

#21

I wonder if there will ever come a day when IPv6 will provide a better web experience than IPv4. At the moment pretty much every website is reachable via IPv4 but a lot not via IPv6. Will there be a day when this turns around?

Faster webrtc establishments and other negotiated connections. CGNAT means more relayed than P2P connections so it should be possible to have more direct traffic for services that want to save that bandwidth.

Re: Google Hits 50% IPv6

#22
post #20

Meanwhile T-Mobile/Odido in the Netherlands is still not supporting IPv6 despite promising to have been working on it for years. Ubiquity gateways also seem to not support it sadly. It would be awesome if they supported something like Hurricane Electric’s tunneling.

Huh? Ubiquity has dropped support? I can't believe that, even the older EdgeRouter series supported it.

Re: Google Hits 50% IPv6

#24
I made my homepage (www.makonea.com) support IPv6 too, but the number of people actually using it is much smaller than I expected. Is IPv6 really that widely used? I'm supporting both because I heard it's good to support both, but I'm not sure what the actual benefit is. Sometimes, when behind Cloudflare, I think even if someone connects via IPv6, it ends up coming through as IPv4

Re: Google Hits 50% IPv6

#25
post #17

Great example of how fixing things "the correct way" does not seem to work sometimes. They added those new addresses that can store more information.. but this requires a rewrite of old software to make it work. If they used the old >bolting on top< method by extending ip4 from 4 octets to 8 (or more) octets, then old software could be extended much easier too / probably addresses could be simply mechanically transla…

I never heard this idea before, but more octets would be a lot prettier!!

Re: Google Hits 50% IPv6

#26
post #19

Earlier quoted context omitted.

> a better web experience than IPv4 That's already the case. IPv6 is often faster because most ISPs these days use cgnat for IPv4.

That fraction of a millisecond doesn't meaningfully translate into a better experience for users.

You're assuming the ISP has dimensioned their CGNAT properly and it's not congested.

Re: Google Hits 50% IPv6

#27
post #3

And 32% is all llm/bots using AWS and other "pay for ipv4 IP" use cases.

As someone on the fighting end of scrapers, this is absolutely not true. If anything I should bais towards v6 as the traffic is on par better than v4

Just remove the A record, and nearly all the scrapers disappear. :-) (And then you get one email per month or so that “your host does not resolve in DNS”.)

Re: Google Hits 50% IPv6

#29
post #24

I made my homepage (www.makonea.com) support IPv6 too, but the number of people actually using it is much smaller than I expected. Is IPv6 really that widely used? I'm supporting both because I heard it's good to support both, but I'm not sure what the actual benefit is. Sometimes, when behind Cloudflare, I think even if someone connects via IPv6, it ends up coming through as IPv4

It's good to support it to resolve the chicken egg problem. If no service supports it, there is no sense in deploying it to the customers and the other way around.

Also you made the life better of people who have DS lite. They only get a public IPv6 and all their IPv4 traffic goes through a CGNAT.

Re: Google Hits 50% IPv6

#30

Earlier quoted context omitted.

Something is very wrong with your network then. I never needed to disable IPv6. Maybe you should question it.

Fair enough. I do question it often. It's a standard Asus router but it's given me a lot of ire. I hate to say it but it's never a problem when I install windows on the same machines (I'm currently in the process of trying to completely remove windows from my life)

There are maybe many buggy routers still out there that reset the IPv6 flow label field when they shouldn't, breaking hash-based load-balancers (the symptom is TCP connections spontaneously reset).

IIRC, a workaround was to prevent Linux from setting this field, or force-reset it on every outbound packet using netfilter.

Post reply on HN