I tried living entirely on IPv6 for a day, and here's what happened
I tried living entirely on IPv6 for a day, and here's what happened
15 comments
-
-
The goal today isn’t to make single stack IPv6 internet practical, it’s to make dual stack ubiquitous. Once that’s achieved, the cost differential, and the increasing technical burden of maintaining IPv4 hacks, will reach a tipping point where it’s relegated to legacy status, but this is at least a decade away, with likely another decade of inertial decay of public IPv4 after that.
-
My ISP doesn't provide IPv6, and with other ISP using CGNAT instead don't think that IPv6 will be the main standard any time soon.
It's more of "if it works, don't fix it", just apply workarounds like tunnels -
yeah, I don't see the benefits of moving to ipv6 outweighing the costs
-
What do you imagine the "cost" is?
-
I'll paste a comment that illustrates it better than I could
Imagine this scenario - you're a corporate with 1000 sites and maybe 5000 networking devices. You have a rolling replacement program for those devices as they become end of life, and as that progresses you reach a point where all of them can work with IPv6. So you switch off IPv4 and work only with IPv6.
Then your corporate acquires another entity, say consisting of 100 sites with 500 devices. All of those devices need checking that they can work on IPv6 and a significant number need replacing at maybe an average of £5000 per device. With IPv4 you can still integrate the legacy kit into your estate without swapping any of it out, with IPv6 only you can't.
For an end user, a small startup, or similar sure go ahead and use IPv6, but there are significant obstacles for larger estates, which is one reason IPv4 isn't going anywhere soon.
-
-
-
-
IP being scarce is a business. It makes so IPS could charge outraging amounts of money for a stable exclusive IP. I do think many people don't want to let the golden cow die. Specially if there's a migration cost.
-
I blocked all my IPv6 because android/Google would always force it's own DNS on me. And I couldn't find a reliable method without rooting the phone to turn this off.
Well i did find one, to disable IPv6 on the router. Is this a thing anyone else had or did i remember it wrong or not dig deep enough?-
For me, working DNS is just managing to connect to DNS-censored piracy sites. And just providing v4 and v6 IP adresses on the DNS field worked IIRC. Also you can use an actual DNS hostname managed to get sites to work.
-
15 comments
I think the fundamental problem with ipv6 is that it's a bit more complex to learn than ipv4 and not universally deployed at the remote host/server level.
New cloud companies who want to be competitive have to purchase ipv4 blocks at significant cost reducing their ability to compete with the incumbent players.
So if you go 100% ipv6 at home, some percentage of the internet will be inaccessible to you unless you employ some workarounds.
We'll drop ipv4 quite fast once everything is up on ipv6 because nearly every modern network enabled device supports it.
The only reason I think we've not gotten over the hump is because our alternatives are still easy enough to work with and nobody requires it.
Only if Chrome announces that the IPv6 version will be the default and the IPv4 version must be manually activated in the future.
All companies announce migration to IPv6