My understanding is it’s no longer that critical. The sky is no longer falling on IPv4
Comment on Yearly reminder that github still does not have an IPv6 address (2023)
Wats0ns@programming.dev 11 months agoBut why ?
whoisearth@lemmy.ca 11 months ago
orangeboats@lemmy.world 11 months ago
The numerous CGNAT deployed worldwide suggests otherwise.
astral_avocado@programming.dev 11 months ago
I am not a full network engineer so take my opinion with a grain of salt. From what I understand, NAT with IPv4 works really really well to mitigate IPv4 address exhaustion. Then there’s an issue with the amount of extra processing switches and routers need to do IPv6, we’re going from 32 bits to 128 bits which is a huge increase and for switches and routers that are handling packets as fast as technically possible with a low amount of resources typically, that’s a not insignificant hurdle.
It’s just easier to do IPv4 in every way, plus that’s what the world’s been using and is used to.
orangeboats@lemmy.world 11 months ago
You can’t talk about NAT and then mention speed in the same statement…
The 128-bit IPv6 addresses are just four simple 32-bit integers if you think about it, but with NAT you have juggle around and maintain the (internal IP, internal Port, external IP, external Port, Protocol) tuples all the time. That’s a significant overhead. Also, switches typically deal with the Layer 2 stuffs. IP is Layer 3.
See the HN discussion for more information.
Except when you have to NAT transversal. Then you are in a world of hurt.