News for hackers. Stuff that matters.
Re:250M-plus reserved IPv4 addresses could be released by sgjohnson on Friday February 09, 2024 @11:33AM (#39316605)
It’s not going to happen. Plenty of routers and other equipment are hardcoded to not route to those addresses. Any time spent rectifying this is time wasted on just adopting IPv6.

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.

Re:250M-plus reserved IPv4 addresses could be released by yardstick on Friday February 09, 2024 @12:45PM (#39317845)
All OpenWRT based routers have supported it for a very long time now.

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.

Re:250M-plus reserved IPv4 addresses could be released by sgjohnson on Friday February 09, 2024 @12:57PM (#39318007)
> 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.

Yes. But it wasn’t. Making this proposal a day late and a dollar short.

Re:250M-plus reserved IPv4 addresses could be released by yardstick on Friday February 09, 2024 @05:52PM (#39321478)
Well, I would put a dollar on this proposal being made again and again over the years to come. It’s still not too late.
Re:250M-plus reserved IPv4 addresses could be released by RockRobotRock on Friday February 09, 2024 @12:50PM (#39317909)
Why do we need more RFC1918 addresses? What's wrong with 10.0.0.0/8?
Re:250M-plus reserved IPv4 addresses could be released by stuff4ben on Friday February 09, 2024 @12:52PM (#39317945)
Some larger companies need it. I say if their equipment supports it and it's currently unused globally, then let it work internally.
Re:250M-plus reserved IPv4 addresses could be released by RockRobotRock on Friday February 09, 2024 @12:59PM (#39318042)
Fair enough.
Re:250M-plus reserved IPv4 addresses could be released by christopherh1 on Saturday February 10, 2024 @06:38AM (#39325430)
This proposal is not regarding repurposing 240/4 as RFC1918 space. It is regarding reclassifying it as Unicast space. I would recommend reading the article.
Re:250M-plus reserved IPv4 addresses could be released by RockRobotRock on Saturday February 10, 2024 @05:00PM (#39330635)
My bad. I was replying to the parent comment but you're right that I should have read the article.
Re:250M-plus reserved IPv4 addresses could be released by austin-cheney on Friday February 09, 2024 @01:17PM (#39318268)
If its just about internal networks then just use a nonrouteable IP. Its not like there are a shortage addresses in the 10.0.0.0/8 network. That is almost 17 million addresses you can do anything with. Somehow if you do run out then just add an extra router and suddenly you have another almost 17 million addresses.
Re:250M-plus reserved IPv4 addresses could be released by growse on Friday February 09, 2024 @02:26PM (#39319258)
"just add an extra router".

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.

Re:250M-plus reserved IPv4 addresses could be released by austin-cheney on Friday February 09, 2024 @02:48PM (#39319605)
The networks could not overlap if the given range does not route. Anyways, that misses the point as the challenges of configuring the corresponding routing table would be trivial compared to managing 16 million devices on a single internal network.
Re:250M-plus reserved IPv4 addresses could be released by yardstick on Friday February 09, 2024 @05:57PM (#39321534)
I’ve worked with large organisations that have merged dozens of companies networks. There were lots of clashes.

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.

Re:250M-plus reserved IPv4 addresses could be released by justsomehnguy on Friday February 09, 2024 @01:09PM (#39318170)
> So for a quick win, Windows just needs to drop special checks they do for 240/4.

Notging special because it's actually in the routing table, as it should be.

Issue ROUTE PRINT to see it yourself.

Re:250M-plus reserved IPv4 addresses could be released by yardstick on Friday February 09, 2024 @06:01PM (#39321561)
Haven’t checked in a couple years, but can you assign a 240.0.0.1/24 for example to the local NIC on Windows?
Re:250M-plus reserved IPv4 addresses could be released by justsomehnguy on Saturday February 10, 2024 @08:18AM (#39325930)
Assigning is another deal (tested on 2012R2):

    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.
Re:250M-plus reserved IPv4 addresses could be released by dtaht on Friday February 09, 2024 @10:05PM (#39323169)
There are several proposals. The most current one merely advocates that 240/4 be moved from reserved for future use to unicast status, which is the deployed reality today.

I hate the idea of wasting 6% of the original internet on rfc1918 space.

Re:250M-plus reserved IPv4 addresses could be released by yardstick on Saturday February 10, 2024 @04:08AM (#39324730)
Given it is already used internally, it cannot be used as public space. The only practical option for it is RFC1918.
Re:250M-plus reserved IPv4 addresses could be released by christopherh1 on Saturday February 10, 2024 @06:37AM (#39325422)
If people are using space that has been marked as "Reserved For Future Use" within their networks, then this is a problem that they must deal with and it must not affect or influence global usage. What about networks squatting on DoD /8 space? Does this mean the DoD can never route this space publicly because people are using it internally?
Re:250M-plus reserved IPv4 addresses could be released by yardstick on Saturday February 10, 2024 @02:06PM (#39329212)
DoD space /8 is different as it is within the public space of IPv4, even if it was never advertised globally.

Whereas 240/4 was never declared public.

Apples and Oranges.

Re:250M-plus reserved IPv4 addresses could be released by christopherh1 on Tuesday February 13, 2024 @02:24AM (#39355405)
You are correct, 240/4 was never marked as public space, it was marked as Reserved for Future Use. Network operators squatting on 240/4 space should have never done so as it was not decided as to what it was going to be used for, hence its current status.

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.

Re:250M-plus reserved IPv4 addresses could be released by christopherh1 on Saturday February 10, 2024 @04:58AM (#39324970)
Our proposal isn't for 240/4 to be reclassified as RFC1918 space, it's for it to be reclassified as unicast space.
Re:250M-plus reserved IPv4 addresses could be released by kees99 on Friday February 09, 2024 @12:01PM (#39317123)
> 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.

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?

Re:250M-plus reserved IPv4 addresses could be released by tjoff on Friday February 09, 2024 @12:36PM (#39317705)
You can still connect to other non-nated individuals that might not expect that.
Re:250M-plus reserved IPv4 addresses could be released by WarOnPrivacy on Friday February 09, 2024 @12:37PM (#39317734)
> On the other hand, as an ISP, you can pull some of those addresses for your CGNAT's external address pool.

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.

Re:250M-plus reserved IPv4 addresses could be released by p1mrx on Friday February 09, 2024 @12:43PM (#39317823)
CGNAT will become common for residential IPv4, because math.

It's more reasonable to expect ISPs to provide native IPv6 alongside CGNAT, than avoid CGNAT entirely.

Re:250M-plus reserved IPv4 addresses could be released by WarOnPrivacy on Friday February 09, 2024 @01:05PM (#39318126)
> CGNAT will become common for residential IPv4, because math.

Oh and thanks for inserting this dystopic hellscape into my awareness, btw. I hope you're wrong for a long time.

Re:250M-plus reserved IPv4 addresses could be released by WarOnPrivacy on Friday February 09, 2024 @12:51PM (#39317927)
> It's more reasonable to expect ISPs to provide native IPv6 alongside CGNAT, than avoid CGNAT entirely.

You'd think so but of our fiber ISPs, 0 of 8 support IPv6 or have plans to do so - inc the NATty ones.

Re:250M-plus reserved IPv4 addresses could be released by p1mrx on Friday February 09, 2024 @12:57PM (#39318021)
Well, expectations do not always match reality.

I suggest that you complain about their lack of IPv6, and encourage other customers to do the same.

Re:250M-plus reserved IPv4 addresses could be released by kees99 on Friday February 09, 2024 @12:08PM (#39317242)
...and about that part:

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

Re:250M-plus reserved IPv4 addresses could be released by Ekaros on Friday February 09, 2024 @12:11PM (#39317289)
We do. With gTLDs they can hoard all the domains under there... And price them how they like.

Then again, we can generate nearly infinite amount of gTLDs so it is not too big deal.

Re:250M-plus reserved IPv4 addresses could be released by dtaht on Friday February 09, 2024 @10:08PM (#39323186)
I am bugged that the BEAD programs do not seem to grok that we are indeed out of IPv4 space, and that the federal government is sitting on 10? 11 idle /8s.
[dead]
Re:250M-plus reserved IPv4 addresses could be released by growse on Friday February 09, 2024 @12:06PM (#39317212)
> Make them all inter-compatible and backward-compatible by modifying the packet structure to accept a variable length address.

"Simply draw the rest of the Owl".

Re:250M-plus reserved IPv4 addresses could be released by mike256 on Friday February 09, 2024 @12:09PM (#39317255)
And a real IPv6 (128 bit) address would look like 164.32.74.105.164.32.74.105.164.32.74.105.164.32.74.105
Re:250M-plus reserved IPv4 addresses could be released by Workaccount2 on Friday February 09, 2024 @12:04PM (#39317170)
Like clockwork this comment shows up...
Re:250M-plus reserved IPv4 addresses could be released by Macha on Friday February 09, 2024 @12:12PM (#39317313)
Often it's even the same users, as if all the reasons it wouldn't work were't explained to them the last times they reflexively suggested it at the mention of IPv6:

https://news.ycombinator.com/item?id=39100317

https://news.ycombinator.com/item?id=36996003

https://news.ycombinator.com/item?id=35047061

...

Re:250M-plus reserved IPv4 addresses could be released by Ekaros on Friday February 09, 2024 @12:06PM (#39317205)
Can you explain exactly how a IPv4 host would send packet to 1.2.4.5.6. What fields inside a fixed IP packet it would set to achieve such?
Re:250M-plus reserved IPv4 addresses could be released by p1mrx on Friday February 09, 2024 @12:24PM (#39317504)
You post a strawman IPv6 address to HN every month or so. Why not take a minute to learn what a real address looks like?

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.

Re:250M-plus reserved IPv4 addresses could be released by dheera on Friday February 09, 2024 @01:28PM (#39318396)
Because nobody has fixed the bad UX yet, I'm still on IPv4, and like 5 million other people, have no incentive to move to IPv6 until the consortium of PMs of IPv6 do some user research (e.g. read HN) and work together to make the UX better or invent a better successor that people actually want to use.

They're all wondering why IPv6 adoption is so slow, I'm telling them right here plain and simple.

Re:250M-plus reserved IPv4 addresses could be released by p1mrx on Friday February 09, 2024 @01:49PM (#39318694)
You're trying to close the door after the horse has left the barn and started a worldwide colony of horsepeople.

IPv6 isn't perfect, but it's not really practical to change the fundamentals of a 25 year old protocol.

Re:250M-plus reserved IPv4 addresses could be released by JackSlateur on Friday February 09, 2024 @12:16PM (#39317376)
By that logic, ipv6 would be 1.2.3.4.1.2.3.4.1.2.3.4.1.2.3.4

Easy to remember, indeed

Re:250M-plus reserved IPv4 addresses could be released by Macha on Friday February 09, 2024 @12:18PM (#39317398)
Address with patterns are indeed easy to remember, see how easy 1:2:3:4:: is to remember. So all we have to do is allocate everyone an artisanally crafted address with easy to remember patterns /s
Re:250M-plus reserved IPv4 addresses could be released by exe34 on Friday February 09, 2024 @12:33PM (#39317665)
Have you heard of domain names? They can be very memorable!
Re:250M-plus reserved IPv4 addresses could be released by dheera on Friday February 09, 2024 @01:30PM (#39318443)
- 8.8.8.8 is IPv4 google DNS

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

Re:250M-plus reserved IPv4 addresses could be released by JackSlateur on Friday February 09, 2024 @02:51PM (#39319637)
And why on earth would you remember 8.8.8.8 in the first place ?

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

Re:250M-plus reserved IPv4 addresses could be released by growse on Friday February 09, 2024 @02:28PM (#39319296)
It's Google's prefix (`2001:4860:4860`) with `8888` and `8844` on the end.

If you can't remember that, the problem's not the protocol.

Re:250M-plus reserved IPv4 addresses could be released by bigfatfrock on Friday February 09, 2024 @01:17PM (#39318269)
And here I was excited, me, as a common person, could possibly buy a block of ipv4. Dream crusher.
Re:250M-plus reserved IPv4 addresses could be released by dtaht on Friday February 09, 2024 @10:07PM (#39323181)
I wish I had enough clout - as jon postel did - to merely declare I was the authority on 255/8 and was selling /24s at an auction price to anyone that was willing to route it. I´d use the money to support open source, and to help fund the rest of the ipv6 transition. And buy myself a nice sailboat to sail around in whilst I de-bufferbloated the rest of the networks of the world.
Re:250M-plus reserved IPv4 addresses could be released by dtaht on Friday February 09, 2024 @10:04PM (#39323168)
240/4 for windows is a patch tuesday away.