Comment on IPv6 for self hosters
avidamoeba@lemmy.ca 1 week ago
I think I’ll die using IPv4 behind NAT along with VPN. 😂
Comment on IPv6 for self hosters
avidamoeba@lemmy.ca 1 week ago
I think I’ll die using IPv4 behind NAT along with VPN. 😂
possiblylinux127@lemmy.zip 1 week ago
Why?
sirboozebum@lemmy.world 1 week ago
What is the impetus for change?
The things you listed are nice but not game changing for most people.
Ephera@lemmy.ml 6 days ago
I don’t have much experience with IPv6 yet either, but as I understand, the primary benefit is that you can get rid of a lot of the crappiness of IPv4, which you might just deem ‘normal’ at this point, like NAT and DHCP. It does happen quite a bit, for example, that we’d like a unique identifier for a host, but with IPv4, you need to store a separate UUID to accomplish that.
billwashere@lemmy.world 1 week ago
Likely because they’re old and resist change like me?
Seriously though it’s such a shift from what I understand I’m very reticent to even start the process. I have a lab at work though that I should really start playing with it at no real risk to anything production. You know what, I’m going to do that next week! Yeah, progress.
First docker and now IPv6. I’m so cutting edge 🤣
avidamoeba@lemmy.ca 1 week ago
Because I have to learn, understand what you wrote, probably more, and especially internalize its security implications. I currently understand all that for IPv4 and I’m confident I’m not leaving holes open when I self-host services. But of course it’s probably a good idea to learn and use IPv6. It’s just not free and when you have existing infrastructure and muscle memory on IPv4, there’s that much more work. If I was starting anew, I’d probably do it.
Appoxo@lemmy.dbzer0.com 6 days ago
And good luck trying to remember the IP in IPv6.
I would believe DNS is now mandatory when you want to implement IPv6?