Also note the proposal is for 240/4 to be added to the RFC1918 list, not to be globally routable.
I’ve been using 240/4 successfully in internal networks for over a decade now. The only devices I’ve had problems with are Windows. So for a quick win, Windows just needs to drop special checks they do for 240/4.
I recall the 240/4 idea being floated at least 5-10 years ago. If Windows was changed to allow it at that point, today hardly anyone would be complaining that Ciscos or Junipers or other core routers don’t support it.
Don’t let perfect be the enemy of good.
Yes. But it wasn’t. Making this proposal a day late and a dollar short.
I think when conceiving of potential issues with this, or thinking about the possible problems of trying to merge two overlapping networks together, your imagination is coming up a little short.
It's never that simple.
I’ve also worked with companies where their networks filled up almost all the 10/8 space and they were running out of room. Having to do things like shrink subnets at individual locations and deal with issues around not able to install all the equipment they originally wanted. It’s a real pain.
And yes, the entire 10/8 space needed to be routable through to the corporate support desk, SIEM tools, payment systems, loyalty systems, security and other IoT systems, etc.
Yes sure you could probably NAT things, or switch to tools/approaches that don’t require every device to have an internally routable IP, but then that’s a terrible argument akin to arguments against IPv6.
Notging special because it's actually in the routing table, as it should be.
Issue ROUTE PRINT to see it yourself.
netsh interface ipv4>add add "4084" 200.0.0.1 255.255.255.0
netsh interface ipv4>add add "4084" 240.0.0.1 255.255.255.0
The parameter is incorrect.
netsh interface ipv4>sh add 4084
Configuration for interface "4084"
DHCP enabled: No
IP Address: 200.0.0.1
Subnet Prefix: 200.0.0.0/24 (mask 255.255.255.0)
InterfaceMetric: 10
The GUI interface explicitly tells to use 'from 1 to 223' for the first octet.I hate the idea of wasting 6% of the original internet on rfc1918 space.
Whereas 240/4 was never declared public.
Apples and Oranges.
Like I said, if people squat on reserved space and the status changes, that's too bad for them if it's reallocated and made routable. Network operators have no right to dictate that space cannot be made routable, simply because they are using space internally and against current policies.
On the other hand, as an ISP, you can pull some of those addresses for your CGNAT's external address pool. Your customers' gear will never see those. Server side will, though. But then, troubleshooting cloud/server front-end to let those through sounds like a more doable chore?
You're right but ugh, CGNAT. We just had fiber deployed here (yay!) and then I got assigned an ISP that has me behind CGNAT. The list of things that can make icky Spectrum better than fiber (for me) is super short, but CGNAT in the 1 or 2 spot.
It's more reasonable to expect ISPs to provide native IPv6 alongside CGNAT, than avoid CGNAT entirely.
Oh and thanks for inserting this dystopic hellscape into my awareness, btw. I hope you're wrong for a long time.
You'd think so but of our fiber ISPs, 0 of 8 support IPv6 or have plans to do so - inc the NATty ones.
I suggest that you complain about their lack of IPv6, and encourage other customers to do the same.
> advocate for yoinking the v4 space that e.g. the DoD, Daimler, Ford or Apple doesn’t use
Isn't it a travesty that owning a sizeable chunk of limited-supply IP addresses doesn't cost much, but exact same number of (nearly-)unlimited-supply domains does cost dearly per-domain to own?
We don't hear horror stories how somebody is hoarding 16 millions .com domains, right? Too expensive to do so.
Then again, we can generate nearly infinite amount of gTLDs so it is not too big deal.
"Simply draw the rest of the Owl".
https://news.ycombinator.com/item?id=39100317
https://news.ycombinator.com/item?id=36996003
https://news.ycombinator.com/item?id=35047061
...
For example, 2eff:ff:a0ee::/54 is a prefix and 2eff:ff:a0ee::dead:beef is an address within that prefix. It is invalid for "::" to appear more than once, as that would be ambiguous.
They're all wondering why IPv6 adoption is so slow, I'm telling them right here plain and simple.
IPv6 isn't perfect, but it's not really practical to change the fundamentals of a 25 year old protocol.
Easy to remember, indeed
- What is IPv6 google DNS? Hell if I can remember it. 2001:4680:something?
Guess which one is going into the DNS config of a new machine that I have to bring up and am forced to deliver results on short notice.
For almost all the thing, I use DNS For DNS resolvers, I use root servers
Never shall I use 8.8.8.8 : why would I ..
If you can't remember that, the problem's not the protocol.
Ping 240.whatever.whatever.whatever from Windows. You just can’t. General failure.
And Windows is not the exception here.
They can lobby all they want, all the effort is going to be in vain. Imagine having to debug a problem where your services are sitting on 240.0.0.0/4, but some customers have routers that just drop the packets to that destination. It’d be a nightmare and “get better networking gear” might not even be a solution, because their ISPs routers could also be doing that.
This proposal is provably worse than just adopting IPv6, because when IPv6 works, it just works. This? This would fragment the IPv4 internet with undefined behaviour.
If they really want more v4 space, they should advocate for yoinking the v4 space that e.g. the DoD, Daimler, Ford or Apple doesn’t use. And they have a lot of v4 space. But that’s also not going to happen, and one of the reasons why not would be similar. A lot of people are actually squatting on DoD space in their internal networks if they run out of 10/8.