this post was submitted on 05 Feb 2024
189 points (95.2% liked)
Technology
58150 readers
4080 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
The entire internet is configured to work with IPv4. Some of the internet (less than a quarter) is also configured to also work with IPv6.
Imagine if your home had two driveways on different streets. Do you tell everyone both addresses, or do you pick one of them? Probably just one right? Now imagine if the second address can only be reached if someone has an off road capable vehicle. And you don't know what vehicle someone has - which address would you give them? Is it even worth having two driveways?
That's the situation we're in. IPv4 support is required and works perfectly. IPv6 is optional and doesn't always work.
Except it doesn't work perfectly, because it has a relatively small address space. That's why ipv6 exists.
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.
Great analogy, thanks
“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.
192.169.x.x will always be easier than fe80:x:x::x:x
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.
(I can never remember the class B private address space, though. Only classes A and C. Never needed to bother with the class B space when you can subnet 10.x.x.x so much.)
No. It's 23 or 42.
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:c0deor192.168.0.2, and my NAS isfe80::coo1:da1aor192.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:c0deand have my IPv6 prefix on a keybind, but I understand that's a bit of a stretch.I have never thought of writing things with static ipv6.
I have been missing out.
You're missing out your
::cafe'sfe80::dead:beef
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.