Live data from Hacker News

Who is squatting IPv4 addresses?

blog.benjojo.co.uk

191–200 of 208 posts

Re: Who is squatting IPv4 addresses?

#191

I don't understand why was the next version of IP not just identical to IPv4 but with more bits in address space? Were they trying to do too many things at once in the 90's?

Dan Bernstein (the famous DJB) asked exactly the same question when IPv6 was standardized:

https://cr.yp.to/djbdns/ipv6mess.html

There still hasn't been a coherent answer. The best approximation is that a lot of networking researchers saw their once-in-a-lifetime opportunity to bikeshed the lowest layer of the public network stack, and couldn't resist the urge.

All of this could have been avoided by making NAT64 part of the original IPv6 standard (instead of wasting a decade pretending like it wasn't necessary) and making it a mandatory service provided by every IPv6 router, unless all downstream routers already provide the service. This would have forced an invisible-to-endpoints IPv6 transition, starting at the backbone ("no default route" region). Carriers would have very quickly pushed the NAT requirement downstream (away from the default-free region) in order to offload the burden it creates. Each step of the transition would have been a strictly local change between two peers, one of which is paying the other, and can therefore can be incentivized ("hey, if you run NAT64 for your downstreams so we don't have to, we will charge you less per month"). No global coordination, and the local coordination is always across a commercial relationship where a carrot can be dangled.

But instead we got what is basically a flag day, so "the transition" will never ever happen. We'll still be talking about it in twenty more years.

Re: Who is squatting IPv4 addresses?

#192

I don't understand why was the next version of IP not just identical to IPv4 but with more bits in address space? Were they trying to do too many things at once in the 90's?

Dan Bernstein (the famous DJB) asked exactly the same question when IPv6 was standardized: https://cr.yp.to/djbdns/ipv6mess.html There still hasn't been a coherent answer. The best approximation is that a lot of networking researchers saw their once-in-a-lifetime opportunity to bikeshed the lowest layer of the public network stack, and couldn't resist the urge. All of this could have been avoided by making NAT64 part…

IPv6 is pretty much IPv4 with more bits - at least compared to the alternative of the time that was CLNP/DECNet (which had 20byte addresses and is quite different).

And the very slow transition hasn't really anything to do with the standard itself, but with the transition technologies (NAT64 like you mentioned). It would have happened with any of the proposed alternatives. Hindsight and all.. NAT itself wasn't even a thing yet (not an RFC anyway) when IPv6 was being developed. Flag days had worked in the past too, so why not again?

Re: Who is squatting IPv4 addresses?

#193
post #71
post #46

At University where I was working until few years ago we all have had static IP addresses for all of our desktops/laptops.

How is this relevant to public IPv4 squatting?

I just wanted to say that there are many companies/institutions that also seat on large number of IP addresses that they don't use/reuse.

Re: Who is squatting IPv4 addresses?

#194

Earlier quoted context omitted.

But the point is that they're not using it. If it's not addressable from the internet, why not use 10.0.0.0/8 instead?

Here's a little different approach to the issue: because IBM is using IP addresses the way they were intended. Private IP ranges are not a good thing, they are a necessary evil. NAT was developed as essentially a hack, originally more to solve tricky routing situations, but later more to allow broad use of reserved range IPs. But the original intent was always that all hosts would have a unique address, regardless of…

You spoke of one of my most annoying issues as a VPN user. Ultimately I resolved it by myself using a non-standard private IP range at home. Any IT person that might ever use 192.168.0.0/16 space for their VPN network is an absolute masochist.

Re: Who is squatting IPv4 addresses?

#196
post #93

Am I the only one alarmed that WD maintains a public registry (via DNS) of MyCloud device UUIDs, their public IP, and their private IP? How many of those are on networks with exploitable routers? Like, you have an external entrypoint and a target internal IP that you know will contain a trove of potentially interesting data.

I agree that's a ridiculous privacy issue. Definitely a case of poor security to provide a minor inconvenience (access your data from anywhere on the internet).

Didn't they actually recently recommend people disable direct Internet access and UPnP? I believe it was after a vulnerability was discovered in one of their legacy products.

Re: Who is squatting IPv4 addresses?

#198

About 10 years ago, IBM used to use the 9.0.0.0/8 space in basically exactly the same way as one would use 10.0.0.0/8, for internal-only networking. Each workstation got its own 9.x.x.x IP, but it wasn't routable from outside. I hope they stopped doing that, but I doubt it.

GE did the same with 3.0.0.0/8 until they sold it to Amazon. When Amazon started actually using those addresses, it created a situation known internally as the “threepocalypse”.

Re: Who is squatting IPv4 addresses?

#199
post #54

Interesting work, but IMHO anything that extends the life of IPv4 does active harm. I'd prefer if these addresses stay out of the pool so scarcity increases and forces people to upgrade. IPv4 is fundamentally too small, period. There are already more people and computers on Earth than possible IPv4 addresses even if it were perfectly optimally used. It leads us further down a path in which everything is behind increa…

A modest proposal: Turn IPv4 off for one minute a day. Next month, increase it to two minutes, and so on. IPv6 adoption will _soar_.

One popular service could do this to great effect.

Re: Who is squatting IPv4 addresses?

#200

I've said it before. Charge $10/year/ip. Would stop a lot of squatting on unused space and free it up.

Could only be applied to more recently allocated networks and they are already paying some sum per network per year (not that much depending on the region but a non-zero number). However the worst offenders are legacy space that predate the modern RIR system and would be completely unaffected by this, since there is no mechanism to charge them.
Post reply on HN