this post was submitted on 31 Jul 2023
144 points (100.0% liked)
Technology
37717 readers
469 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm going on professional year 24 of clients requiring that IPv6 be deactivated on every device in their network. Whee.
My current ISP still does not offer IPv6 🤦 🤦 🤦
Verizon, my ISP, offers IPv6 in my area but the implementation is broken and it ends up being an order of magnitude slower than simply using IPv4 and HE as an IPv6 tunnel broker.
AT&T is the same. And the last time I looked they don't give you enough address space to host your own subnet. You get a /64 instead of a /56. And it's slower than ipv4.
Every few months I try it out, complain and then switch it off.
Interesting. In NC here. Not sure if there's a difference regionally. I was seeing that kind of RTT on ipv4, but ipv6 was slower. I'll need to give it another try. The last time I did was at my last place where I had the BGW210. I have the BGW320 now and haven't tried on that. Maybe that, or changes in their routing since then will make a difference.
You'd think IPv4 would be the one that requires CGNAT not IPV6... Bizarre...
Yeah, my company totally blocks ipv6 when the VPN is on. Not sure why they're so backward for a tech company.
The same goes for my place of work. It's going to be shit loads of fun when we are forcibly transitioned. I hope before that time I will be doing web development work and kissing my professional career in infrastructure good bye.
What's their rationale? Is there one?
Their network admins are old and don't want to learn new stuff, or their networking equipment is old and they don't want to replace it.
IPv6 existed when I was a kid. It is not even remotely new.
I know, but it wasn't commonly used until IPv4 depletion became a more serious issue.
I must've said this at least 10 years ago: the more people move to IPv6, the more IPv4 are left free, so the less reason for moving to IPv6.
The "migration" could easily take several more decades.
We were talking about it when I was in undergrad.
Yeah, but for all we know you went to college thousands of years in the future, Time Lord.
That is why I think IPv6 is a non-starter. ;)
"Compliance with regulations."
Is there really any problem with that on the internal though?