Live data from Hacker News

AWS adds an extra 5.5M IPv4 addresses

github.com

71–80 of 283 posts

Re: AWS adds an extra 5.5M IPv4 addresses

#71

The DoD still owns 14 class A blocks, right? And is 240.0.0.0/4 still "reserved"?

Yes, and it may be possible they will be sold[1]. From the article it looks like they're identifying unauthorized use of their space, while clearing the addresses from firewalls to become really routable.

[1]: https://arstechnica.com/information-technology/2021/04/penta...

Re: AWS adds an extra 5.5M IPv4 addresses

#72
post #53

Earlier quoted context omitted.

Why should I want people to be accessing my personal desktop/laptop/tablet?

It's cause you want to get to your home boxen from outside.

Surely you know this is a super niche requirement?

You can use IP6 or a commercial rather than domestic ISP if you really need to do it.

Re: AWS adds an extra 5.5M IPv4 addresses

#73
Last October, Amazon bought ~4 million addresses by bribing the corrupt technocrats of a radioamateur "non-profit" organization. Fuck Amazon, fuck those corrupt technocrats (like the ICANN/.org team who tried to sell the TLD). It's incredible what this kind of people can get away with.

Previous discussion on HN: https://news.ycombinator.com/item?id=24753654

Re: AWS adds an extra 5.5M IPv4 addresses

#74

Earlier quoted context omitted.

Problem with CGNAT is the costs involved in bookkeeping for law enforcement. Where an IPv4 solution for your clients only needs change-logging on IPbinding-to-client level, the CG-NAT requires you as an ISP to log every outgoing IPv4/port combination with timestamp to client mapping. Which requires A LOT more storage and much more expensive equipment. Going rate per IPv4 is up to $40 nowadays, selling of your v4 bloc…

Anything that makes mass surveillance more expensive is a plus in my book.

Whilst I don't necessarily disagree with the sentiment, all the costs an ISP might incur will almost certainly be passed into the consumer. We're paying to be surveilled in many different ways.

Re: AWS adds an extra 5.5M IPv4 addresses

#75
post #31

Earlier quoted context omitted.

Yeah I would like the FTC go after new IPv4 deployments / mandate dual stack on anti-trust grounds.

How does IPv4's use translate to anti-trust?

Promoting the continued dominance of a standard which causes artificial scarcity.

Re: AWS adds an extra 5.5M IPv4 addresses

#76
post #61

Earlier quoted context omitted.

Disclaimer: I work with this stuff and might be a little biased to certain vendor solutions. A good CGNAT implementations have support for static blocks: the subscriber always ends up a a specific ipnumber+portblock combination. (Each subscriber is assigned a specific number of exit ports and this all just logged once during startup so you always know where each subscriber ends up). Should they run out of their assig…

And law enforcement inquiries barely contain source port information, or precise time. Most of then go like: who had this IP in $this-two-weeks-window. No source port, no destination IP/port.

that will just lead to a whole lot of "we dont have that information" or alternativly, "all of these 10000 people used that, have fun!"

Re: AWS adds an extra 5.5M IPv4 addresses

#77
post #61

Earlier quoted context omitted.

Disclaimer: I work with this stuff and might be a little biased to certain vendor solutions. A good CGNAT implementations have support for static blocks: the subscriber always ends up a a specific ipnumber+portblock combination. (Each subscriber is assigned a specific number of exit ports and this all just logged once during startup so you always know where each subscriber ends up). Should they run out of their assig…

And law enforcement inquiries barely contain source port information, or precise time. Most of then go like: who had this IP in $this-two-weeks-window. No source port, no destination IP/port.

"We don't have the ability to determine a specific subscriber based on the information provided" and close the request.

Re: AWS adds an extra 5.5M IPv4 addresses

#78
post #61

Earlier quoted context omitted.

And law enforcement inquiries barely contain source port information, or precise time. Most of then go like: who had this IP in $this-two-weeks-window. No source port, no destination IP/port.

that will just lead to a whole lot of "we dont have that information" or alternativly, "all of these 10000 people used that, have fun!"

And isn't that the privacy we all would really enjoy? :D

Re: AWS adds an extra 5.5M IPv4 addresses

#79

Last October, Amazon bought ~4 million addresses by bribing the corrupt technocrats of a radioamateur "non-profit" organization. Fuck Amazon, fuck those corrupt technocrats (like the ICANN/.org team who tried to sell the TLD). It's incredible what this kind of people can get away with. Previous discussion on HN: https://news.ycombinator.com/item?id=24753654

Well, if that organisation didn't have a use for those addresses... I don't see what the big deal is.
Post reply on HN