There are huge gaps in ipv6 adoption which means most users and services must continue to support and use ipv4.
Since everyone has to continue ipv4 support, there’s not much motivation to push general adoption of ipv6. Maintaining dual stack support has its own costs.
Even within AWS, many of their services still don’t support ipv6. AWS fees for ipv4 addressing may end up being a comparatively big driver for adoption.
abhibeckert@lemmy.world 9 months ago
IPv6 is here, and has been for a long time. But if, for example, your web or email server can only be reached over IPv6 some people will not be able to load the site or send emails to you.
There’s nothing really you can do about it, it’s just a matter of waiting for hundreds of millions of individual system administrators, to get their act together and configure their systems to work with IPv6.
elrik@lemmy.world 9 months ago
Except it doesn’t work perfectly, because it has a relatively small address space. That’s why ipv6 exists.
otp@sh.itjust.works 9 months ago
The driveway works perfectly, but it doesn’t have space for all the guests if they all want to use their own vehicles.
Thankfully, we have carpooling and rideshares.
FoolHen@lemmy.world 9 months ago
Great analogy, thanks
KairuByte@lemmy.dbzer0.com 9 months ago
“Luckily” we are reaching the point where IPv4 just isn’t going to be fiscally sustainable for the majority of companies, meaning the push to IPv6 will be hastened.
Though I don’t pretend it isn’t going to be a hell of a ride.
___@lemm.ee 9 months ago
192.169.x.x will always be easier than fe80:x:x::x:x
frezik@midwest.social 9 months ago
I had a roommate once who need an IP for something, and because it was a device I had been working with recently, I just rattled off “192.168.0.7” or something.
He was in awe of the fact that I could remember it. However, it’s not that difficult when you know the private prefix you use is always “192.168.” and that gets burned into your brain. The next octet is often zero (maybe 1 if your home network gets crazy), and you really only need to remember the final octet for the device.
Point is, fe80::x will go the same way. You’ll remember fe80, and the rest is however you handled your own network scheme.
SteveTech@programming.dev 9 months ago
I definitely agree with automatically configured stuff, but I enjoy setting link-local static IP address with IPv6, like my home server is
fe80::bad:c0de
or192.168.0.2
, and my NAS isfe80::coo1:da1a
or192.168.0.3
. I’ve definitely mistyped the IPv4 a few times (see your 169 typo), but the IPv6 always delivers hackerman vibes.I have also set
<prefix>::bad:c0de
and have my IPv6 prefix on a keybind, but I understand that’s a bit of a stretch.p1mrx@sh.itjust.works 9 months ago
fd00::x is shorter than 192.168.x.x
Technically you’re supposed to use fdxx:xxxx:xxxx::x, but on your home network nobody cares.