News for hackers. Stuff that matters.

A comment on Amazon, Verizon found using IPv4 240/4 addresses. Parent comment

Re:Amazon, Verizon found using IPv4 240/4 addresses by justusthane on Tuesday August 23, 2022 @10:31PM (#32574323)
Big companies are using groups of IP addresses internally on their private networks which technically aren’t supposed to be used anywhere. This is mostly fine and no one cares too much.
[ Parent | on HN ]
Re:Amazon, Verizon found using IPv4 240/4 addresses by mr_toad on Wednesday August 24, 2022 @12:15AM (#32574915)
> This is mostly fine and no one cares too much.

Until it breaks something, as was the case with 1.1.1.1

[ Parent | on HN ]
Re:Amazon, Verizon found using IPv4 240/4 addresses by 1letterunixname on Wednesday August 24, 2022 @02:01AM (#32575439)
You can't dent the universe without breaking some things. It's inevitable. Adapt. Overcome. It'll be okay.
[ Parent | on HN ]
Re:Amazon, Verizon found using IPv4 240/4 addresses by gitrog on Wednesday August 24, 2022 @03:22AM (#32575934)
Could someone explain how this "breaking" works?
[ Parent | on HN ]
Re:Amazon, Verizon found using IPv4 240/4 addresses by justusthane on Wednesday August 24, 2022 @07:03AM (#32577719)
If 240/0 ends up being assigned as private address space, it won’t matter since that’s how these companies are already using it. If, however, it’s assigned as public address space, then these addresses would potentially (depending on their routing) be unreachable from the networks of the companies already using them as private addresses.
[ Parent | on HN ]
Re:Amazon, Verizon found using IPv4 240/4 addresses by XionXIV on Wednesday August 24, 2022 @09:49AM (#32579426)
What happened with 1.1.1.1?
[ Parent | on HN ]
Re:Amazon, Verizon found using IPv4 240/4 addresses by justusthane on Wednesday August 24, 2022 @09:58AM (#32579538)
I’m guessing 1.1.1.1 being used as a private IP in cases like this: https://community.cisco.com/t5/wireless-mobility-knowledge-b...
[ Parent | on HN ]