51–60 of 78 posts
All we need is ONE major website to declare 24 Hour brown-out for IPv4 and put a message something like "Contact your ISP to upgrade your connection". Alas, publicly traded companies....
GitHub not being available via IPv6 is the biggest hurdle because so much depends on it.
If only the android devs would implement dhcpv6 ffs.
From the article, in millions of users: Jan 2018 - 513.07 Jan 2019 - 574.02 Jan 2020 - 989.25 Jan 2021 - 1,136 Jan 2022 - 1,207 A growth rate of 24% Looking at Google's IPv6 stats: July 2019 - 29% July 2020 - 33% July 2021 - 36% July 2022 - 42% July 2023 - 44% Or an increase of about 3% each year.
> July 2023 - 44% What's the worldwide average. For the US specifically it's the majority of traffic at 53%: * https://www.google.com/intl/en/ipv6/statistics.html
Earlier quoted context omitted.
Setting up IPv6 on my home network was fun and exciting now it's just boring. The only time I've noticed it was was once when IPv4 broke (dhcp server issue) and another time when IPv6 itself broke (radvd issue). All that said I do sort of wonder when or if we'll ever move off dual stack. I think there's a strong argument that running two protocols at once is riskier then the combined risks of the two.
I can't imagine too many businesses will be switching to it internally unless forced to. ISP's and mobile carriers are one thing.
All we need is ONE major website to declare 24 Hour brown-out for IPv4 and put a message something like "Contact your ISP to upgrade your connection". Alas, publicly traded companies....
GitHub not being available via IPv6 is the biggest hurdle because so much depends on it.
I’d expect GitHub to have moved to Azure since the buyout.
The IPv6 adoption seems more tied to Azure/AWS/GCP support than anything else.
At this point I'm personally convinced that ipv6 is a failed technology. It used to be interesting to see the news about new ipv6 deployments, adoption ratings etc. Now I basically don't care.
ISPs have deployed IPv6 quite successfully now. Barring some legacy connections (DOCSYS 2 or something mostly) that still get no IPv6, basically all new connections have IPv6 as a default, and old ones have either already been migrated (including DSL) or are in the (sometimes long) rollout process. Some tied the IPv6 migration with an IPv4 CGNAT move, which makes IPv6 very attractive: hobbyists have to ride on IPv6 for external reachability, while casual uses like gaming, voip, conferencing, and whatnot benefit from relay-less p2p connections by preferring IPv6.
For the four major ISPs, this report from 2021 shows 89, 71 and 49% active IPv6 on mobile (not just 5G), with a 1% outlier that should have gotten its act together by now, and 99, 89, 53 and 22% for landlines, and projects 99, 93, 80 and 40% deployment in 2023 (which sounds about right for today in my experience), and 99, 97, 95 and 85% deployment for landlines in 2025, at which point CGNAT won't be an issue for most and IPv4 basically becomes legacy technology provided things also move forward server side.
https://www.arcep.fr/cartes-et-donnees/nos-publications-chif...
Earlier quoted context omitted.
NAT is horrible.
Leaned on heavily to protect cheap IOT devices. Could you imagine the bot armies if every IOT device was NOT behind a NAT?
Why? Firewalls have been around since before 1994, when Cheswick and Bellovin literally published the book on firewalls:
* https://en.wikipedia.org/wiki/Firewalls_and_Internet_Securit...
If only the android devs would implement dhcpv6 ffs.
Earlier quoted context omitted.
> July 2023 - 44% What's the worldwide average. For the US specifically it's the majority of traffic at 53%: * https://www.google.com/intl/en/ipv6/statistics.html
Is there a breakdown by network type? e.g. Cellular Network, VPS Provider, Home ISP, IoT, etc... The reason I ask is that last numbers I saw somewhere were thrown off by VPS providers and cellular providers. Cellular had no choice but to go IPv6 due to sheer numbers of users. VPS was easy due to the ephemeral nature of VM's. People could slowly adopt it at their own rate.
How are these situations "throwing off" the numbers?
There seems to an underlying assumption in this statement that if you (e.g.) stream a Youtube video from your cell phone (over IPv6) it is "invalid" (less valid) but if you stream it on your desk/laptop from your (IPv4-only) home or work's ISP it is (more) "valid".
> Cellular had no choice but to go IPv6 due to sheer numbers of users.
Of course they have a choice: they could spent millions of dollars getting IPv4 address for their customers, or they give IPv4 shared space [1] to all the devices and spend millions on CG-NAT equipment. No IPv6 needed.
Every IPv6 connection is just as valid as every IPv4 connection.
If only the android devs would implement dhcpv6 ffs.
Why do you need that? What's wrong with SLAAC and RDNSS?
It's handy in many situation where you want to assign specific devices specific addresses, or at least make a log of dynamically chosen addresses (e.g., networks with auditing requirements).