At University where I was working until few years ago we all have had static IP addresses for all of our desktops/laptops.
Who is squatting IPv4 addresses?
71–80 of 208 posts
Re: Who is squatting IPv4 addresses?
#72At University where I was working until few years ago we all have had static IP addresses for all of our desktops/laptops.
My old uni holds two /16s which are used for clients. Firewalled, but if you use the Wi-Fi there then you are getting your own "personal" IPv4 address per device.
NAT is a cludge, not a security feature.
Re: Who is squatting IPv4 addresses?
#73Like, you have an external entrypoint and a target internal IP that you know will contain a trove of potentially interesting data.
Re: Who is squatting IPv4 addresses?
#74Earlier quoted context omitted.
Then how is it squatting? Even the article defined it as IP space not owned. From the parent article "I will define IP address squatting as “using IP addresses that are not RFC1918 defined and not your unicast space issued by a RIR”." Unless this is meant to construe all legacy assignments as "squatting" which is a pants on head definition.
By analogy, domain squatting isn't using a domain that isn't yours, it's underutilizing a limited resource that's assigned to you. Using IPs for internal networking doesn't necessarily mean under utilizing though; but might not be enough to justify such an assignment today.
But how do you define 'use' they could easily 'use' them by simply announcing them via BGP and null routing the traffic to the IP's they don't want exposed?
The end answer is still IPv6, where everyone can have as much or as little IP space as they want.
Re: Who is squatting IPv4 addresses?
#75Re: Who is squatting IPv4 addresses?
#76Earlier quoted context omitted.
Of a highly constrained resource, they're using a tiny fraction of what they've been given. That's a weird definition of "using what they have." If I asked for a class C for my business running a local corner store, I'd be looked at like I was crazy. IBM gets 16 million public IPs and it's cool? Yeah, I know you can't perfectly use an IP space, but with 128 offices, IBM could give each office an allocation of around…
It may be difficult to understand now, but back in the 90's, addresses were handed out like candy. IBM got their allocation in the late 80's. I worked for a couple of small and mid-sized companies that had /16's and larger. And we barely used a fraction of that space. I have a /24, personally, registered back in 1993. It's routed to my home network. I know several other folks who were on the early internet, and had t…
Re: Who is squatting IPv4 addresses?
#77There are a lot of /24 in use strictly for BGP, even if they're not fully utilized. This is the public address space, though, and not really "squatting"
Re: Who is squatting IPv4 addresses?
#78Earlier quoted context omitted.
Of a highly constrained resource, they're using a tiny fraction of what they've been given. That's a weird definition of "using what they have." If I asked for a class C for my business running a local corner store, I'd be looked at like I was crazy. IBM gets 16 million public IPs and it's cool? Yeah, I know you can't perfectly use an IP space, but with 128 offices, IBM could give each office an allocation of around…
IBM was the original "cloud"... AKA mainframes. They had a LOT of addressed services for decades (still do). If you want to pick on a company for hogging IPv4 space, pick on Apple. They have a /8 and probably aren't using any of it.
Indeed, both apple.com and icloud.com resolve to 17.253.144.10
Re: Who is squatting IPv4 addresses?
#79About 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.
At the same time frame HP did the same with their /8 IIRC