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.
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.