News for hackers. Stuff that matters.

A comment on Reclaiming IPv4 Class E's 240.0.0.0/4. Parent comment

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by tsimionescu on Wednesday May 29, 2024 @02:24AM (#40509078)
They'll still have 10.0.0.0/16 or 172.16.0.0/16 VPCs as the default, even if they can't buy a large enough chunk of IPv4s to easily give out public access through IPv4 (though they'll likely find some way to partner with some ISP that is switching massively to CGNAT and can free up most of the IPs they would normally give to their clients, or something).

IPv4 is far too ingrained to start with IPv6 only.

[ Parent | on HN ]
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by jiggawatts on Wednesday May 29, 2024 @06:42PM (#40517955)
As far back as 2015 I tried to build an all-IPv6 network for a lab environment. It very nearly worked and the few remaining issues would have been quick fixes for vendors.

We’re closer than most people assume.

[ Parent | on HN ]
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by simiones on Thursday May 30, 2024 @06:54AM (#40522254)
I'm not saying it can't work, I'm saying it's no one's first choice, even today. It's just extra risk, less usable (10.0.123.234 vs fd00:ec2::1234:5678), extra hassle (multiple IPs per NIC, extra hoops to access Github, etc).
[ Parent | on HN ]