127.0.0....2?

sots

@Pixels said:

@sots said:

@kevinds said:

@sots said:

@kevinds said:

@sots said:
What will happen if https://blog.apnic.net/2022/05/31/cutting-down-on-ip-address-waste/ ?

That can't happen.. There are way, way too many hosts that won't get updates required for that to work..

Then, do you think APNIC is crazy?

100%

To suggest this, in this decade, they would have to be...

Microsoft's IP stack has refused to use/interact with the Class E addresses since Windows 95 and NT.. Every M$ OS to date would need a patch because there are still some of those systems in use...

There are others, but M$ is the biggest one..

I want to give a smack upside the head to whomever at M$ thought it was a good idea to blacklist the 'For future use' IPs..

Debogon needed.

And why not switch to IPv6 instead of pushing more patches to keep IPv4 afloat

Of course all of my web services support IPv6, but there're still lots of networks without IPv6 support e.g. I'm now staying in a hotel, and its WIFI does not support IPv6, so I have to use warp to access IPv6.

Pixels

@sots said:

@Pixels said:

@sots said:

@kevinds said:

@sots said:

@kevinds said:

@sots said:
What will happen if https://blog.apnic.net/2022/05/31/cutting-down-on-ip-address-waste/ ?

That can't happen.. There are way, way too many hosts that won't get updates required for that to work..

Then, do you think APNIC is crazy?

100%

To suggest this, in this decade, they would have to be...

Microsoft's IP stack has refused to use/interact with the Class E addresses since Windows 95 and NT.. Every M$ OS to date would need a patch because there are still some of those systems in use...

There are others, but M$ is the biggest one..

I want to give a smack upside the head to whomever at M$ thought it was a good idea to blacklist the 'For future use' IPs..

Debogon needed.

And why not switch to IPv6 instead of pushing more patches to keep IPv4 afloat

Of course all of my web services support IPv6, but there're still lots of networks without IPv6 support e.g. I'm now staying in a hotel, and its WIFI does not support IPv6, so I have to use warp to access IPv6.

Yes, unfortunately my ISP doesn't provide IPv6 connectivity on mobile network but it does on fiber. So I Wireguard from my phone to my home and I have v6 on the go that way.

kevinds

@TimboJones said:
That doesn't make sense. If those old ass systems are in place and working today, they don't need any updates. They aren't working with modern encryption or the Internet in general.

Only new stuff going forward would need it, and then obviously only supported stuff. It's not the first time saying "well, you're too old, buy new".

Also, Microsoft OS's, and desktop ones at that, don't tend to be edge routers. The 2012 server versions and later would be fine.

I want to give a smack upside the head to whomever at M$ thought it was a good idea to blacklist the 'For future use' IPs..

That's how it works (future reserved use, duh). Glad you aren't in charge, either.

It doesn't matter if they are routers or not, by being forbidden in the OS, the OS can't access them, so the existing hosts won't be able to access services on the new IPs.

Reserved for future use means they are planned to be used in the future, so don't forbid the OS from using them, because the plan is to use them at some point..

I can use 240.0.0.0/4 IPs in my routers, no problem, Windows can't traceroute or ping them though, nor access any services on them.

They completely fucked the 'for future use' part.

Old Windows, you can still manually update/install the root certificates when you need to.

johnnyquestion

I can use 240.0.0.0/4 IPs in my routers, no problem, Windows can't traceroute or ping them though, nor access any services on them.

I like how Windows gives a Transmit error: code 1231 not host not reachable

kevinds

@johnnyquestion said:
I like how Windows gives a Transmit error: code 1231 not host not reachable

I started using 240.0.0.0/4 IPs for PtP connections between routers, just because I could. Works normally until I need to ping/traceroute/access them from Windows.

So yes, someone at M$ deserves a smack upside the head for that. I fail to see the logic in blacklisting 'for future use' addresses.

TimboJones

@kevinds said:

@TimboJones said:
That doesn't make sense. If those old ass systems are in place and working today, they don't need any updates. They aren't working with modern encryption or the Internet in general.

Only new stuff going forward would need it, and then obviously only supported stuff. It's not the first time saying "well, you're too old, buy new".

Also, Microsoft OS's, and desktop ones at that, don't tend to be edge routers. The 2012 server versions and later would be fine.

I want to give a smack upside the head to whomever at M$ thought it was a good idea to blacklist the 'For future use' IPs..

That's how it works (future reserved use, duh). Glad you aren't in charge, either.

It doesn't matter if they are routers or not, by being forbidden in the OS, the OS can't access them, so the existing hosts won't be able to access services on the new IPs.

You also can't play Call of Duty on Nintendo.

Reserved for future use means they are planned to be used in the future, so don't forbid the OS from using them, because the plan is to use them at some point..

>

Yes, because you/they/OS doesn't know how to use them. If/when they'll get used, then an update will be necessary. That's by design. Hence, the word reserved. If they weren't, people would use them and then won't be used for the reserved purpose.

I can use 240.0.0.0/4 IPs in my routers, no problem, Windows can't traceroute or ping them though, nor access any services on them.

They completely fucked the 'for future use' part.

Old Windows, you can still manually update/install the root certificates when you need to.

We were never supposed to be on IPv4 still in 2022. Also, old Windows lacks entire modern encryption protocol support, it's not just a matter of updating trusted root certificates.

kevinds

@TimboJones said:
You also can't play Call of Duty on Nintendo.

Maybe you can't? I definitely can..

Yes, because you/they/OS doesn't know how to use them. If/when they'll get used, then an update will be necessary. That's by design. Hence, the word reserved. If they weren't, people would use them and then won't be used for the reserved purpose.

How can you say "they won't be used for the reserved purpose"?

People want to use them.. Guess what.. No update... Microsoft will not update the OSs, so they can ever be used.. That is my point.

Reserved doesn't mean forbidden. Unless an IP block has a purpose, it won't be used for anything anyways.

Yes, IPv6 is nice, but it is now 26 (?) years old and it still isn't being used much.. At least it is finally catching on though..

ralf

@TimboJones said:
We were never supposed to be on IPv4 still in 2022.

Citation needed.