Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

IPv6 traffic crosses the 50% mark

google.com

Post reply on HN
Print view View original

371–380 of 643 posts

Re: IPv6 traffic crosses the 50% mark

#371

Post by usui »

kalleboo wrote: post #364
lxgr wrote: post #355

Earlier quoted context omitted.

Wow, that’s very cool! Do you know how that works? Do they just connect you to a NAT64 gateway of your choice?

IPv4 is provided using DS-Lite or MAP-E depending on the provider. I'm using OpenWRT and paid for a static IP so I had to manually configure all the details for the MAP-E tunnel in OpenWRT myself, I think typically the routers sold to consumers pick up the configuration automatically somehow.

Which provider are you using? I'm curious about this since there are not many OpenWrt guides for getting connected in Japan. Is your config similar to this write-up? https://github.com/fakemanhk/openwrt-jp-ipoe

I didn't need to do any configuration for DS-Lite or MAP-E, as DHCPv6 with a configured prefix got IPv6 working, although DNS is still broken when turning off IPv4 entirely.

Re: IPv6 traffic crosses the 50% mark

#373

Post by marginalx »

Is most of that due to mobile?

The real migration challenges are in the server side/consumer home internet space which I'm not sure if there are clear stats around the adoption there.

I think IPV6 is a great example of over engineering, trying to do too much in one iteration. In an ideal scenario this could work, but in the context of large scale change with no single responsible party, it usually doesn't work well.

Re: IPv6 traffic crosses the 50% mark

#374

Post by vlovich123 »

tbrownaw wrote: post #343
jermaustin1 wrote: post #323

Earlier quoted context omitted.

Same with Twilio. We have an internal server that does system alerts. We recently moved it to an IPv6 only host, and a few weeks went by and noticed there were no longer receiving alerts. Turns out we could not connect to Twilio's API which is IPv4 only.

So zero validation after that change?

Zero observability and alerting too. Seems like they’re planning to be a productive future member of that team.

Re: IPv6 traffic crosses the 50% mark

#375

Post by usui »

ectospheno wrote: post #297
usui wrote: post #5

It has barely hit 50% and it's already plateauing. This adoption rate is ridiculous despite basically all network interfaces supporting it. I thought I would see IPv6 take over in my lifetime as the default for platforms to build on but I can see I was wrong. Enterprise and commercial companies are literally going to hold back internet progress around 60 to 75 years because it's in their best interest to ensure users…

> Also, notice how Android and iOS don't support turning off IPv4. You can trivially connect an iOS device via IPv6 only.

Can you share details on how one trivially connects via IPv6 only? I see no option in iOS Wi-Fi settings to do this, and I think it's reasonable to expect not to have to turn off IPv4 on my access point to test IPv6-only networking.

Re: IPv6 traffic crosses the 50% mark

#376

Post by Dagger2 »

ahartmetz wrote: post #292
Dagger2 wrote: post #216

Earlier quoted context omitted.

It's very common. German ISPs collectively went with DS-Lite, so most of that 77% with v6 have CGNATed v4.

Somehow it's really hard to find numbers, but AFAIK at least Telekom and 1&1 don't use CGNAT for home connections, which already rules out that 77% have it.

Questions like this suggest that 1&1 do: https://forum.openwrt.org/t/solved-dsl-over-ds-lite-with-isp...

I'm less sure about Telekom. For obvious reasons, it's hard to find info in English.

Re: IPv6 traffic crosses the 50% mark

#377

Post by rayiner »

jonhohle wrote: post #351
sidewndr46 wrote: post #312

Earlier quoted context omitted.

While we're at what about older physical layers? Coaxial based stuff seems cool in 2026

Isn’t that what MoCa is for?

Isn’t twinax just “I heard you like coax so I put coax in your coax.”

Re: IPv6 traffic crosses the 50% mark

#378

Post by kalleboo »

toast0 wrote: post #321
cyberax wrote: post #127

Earlier quoted context omitted.

IPv6 is a recursive WTF. It might _look_ like a conservative expansion of IPv4, but it's really not. A lot of operational experience and practices from IPv4 don't apply to IPv6. For example, in IPv4 each host has one local net address, and the gateway uses NAT to let it speak with the Internet. Simple and clean. In IPv6 each host has multiple global addresses. But if your global connection goes down, these addresses…

> Then there's IP fragmentation and PMTU that are a burning trash fire. It's not significantly worse on v6 compared to v4. Yes, in theory, you can send v4 packets without DF and helpful routers will fragment for you. In practice, nobody wants that: end points don't like reassembling and may drop fragments; routers have limited cpu budget off the fast path and segment too big is off the fast path, so too big may be dr…

> but there's plenty of derpy networks out there for v4 as well.

God yes, I've helped so many users on PPPoE by telling them to set their MTU to something lower...

Re: IPv6 traffic crosses the 50% mark

#379

Post by strenholme »

rtdq wrote: post #13

And still, in the year of our lord 2026, GitHub does not support IPv6. https://github.com/orgs/community/discussions/10539

Kinda sorta.

github.com doesn’t have an IPv6 address.

github.io does have an IPv6 address. Indeed, one workaround for getting rate limited when using a carrier NAT with github.com is to have a github.io page and pull data from github.io instead of github.com.

Edit: About a decade ago, all of my hosting had full IPv6 support, and I tried to move over to IPv6. However, there was an issue with Letsencrypt certs not validating over IPv6, so I made my web pages IPv4 only. Recently, I gave IPv6 a go again, and the cert issue has been fixed, so now my webpages finally have both IPv4 and IPv6 addresses.

Post reply on HN