this post was submitted on 24 Jun 2024
688 points (97.9% liked)
Programmer Humor
32464 readers
810 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yup, the benefits don't outweigh the costs.
For individuals. There are tons of benefits for everyone collectively, but as is often the case, there's not enough incentive for any one person to bother until everybody else does.
I'd be open to considering those but I never had a website break it down in a material way. At best 6 to me is shiny and side grade -- if it results in major labor and time spent without reasonable benefit within a LAN then it's not going to be a humdinger. Of course like I said if there are arguments to be made I'm happy to contemplate them.
YMMV, for me the juice hasn't been worth the squeeze yet and I'm not sure it ever will.
I use IPv6 exclusively for my homelab. The pros:
No more holepunching kludge with solutions like ZeroTier or Tailscale, just open a port and you are pretty much good to go.
The CGNAT gateway of my ISP tends to be overloaded during the holiday seasons, so using IPv6 eliminates an unstability factor for my lab.
You have a metric sh*t ton of addressing space. I have assigned my SSH server its own IPv6 address, my web server another, my Plex server yet another, ... You get the idea. The nice thing here is that even if someone knows about the address to my SSH server, they can't discover my other servers through port scanning, as was typical in IPv4 days.
Also, because of the sheer size of the addressing space, people simply can't scan your network.
personally, i'd have pretty big benefits for my homelab if i could use my own ipv6 range for everything. having only a singe public IP is just very limiting.
sadly, my ISP does give out ipv6 for home networks, but i cannot connect to any of them from my mobile phone with the same carrier. so that's fun. they talked about rolling out ipv6 on mobile networks years ago, but i guess it'll take a few more....
what costs are there beyond just leaving it on in supported configurations?
YMMV. Time, energy, compat*ability problems, unforseen issues which cost time debugging.
Again, I'm speaking for me -- there has to be a tangible real benefit and within networks even with 100 devices IPv4 does the job better than fine and better than IPv6 for some folks.
Not to mention its just plain easier to remember 4 octet sets of numbers running from machine to machine in an office than 6 or 8 or whatever.