5 ms·

JEDI was a deal for internal cloud infrastructure. I don't think they would be utilizing public IP address ranges.

• 1MachineElf 5y ago
  Good point, but, here's an anecdote to serve as a counterpoint: When I was at a US three-letter department from 2013-2015, they did in fact use non-private IPs for their internal datacenter networks, and even for their office space LAN DHCP lease ranges. It blew my mind when I looked at my laptop and saw a public IP on it's ethernet interface. Watching the realization dawn on my InfoSec peers' faces there was amusing as well. IT personnel way up in the hierarchy blessed with institutional knowledge confirmed to me that using public IPs everywhere is one thing they did to justify sitting on that many public IPv4 addresses. They seemed confident that their firewalls and routing configurations were enough to protect their self-drawn boundary lines, and in many ways, they were right. It also made inter-agency connection agreements quite simple. So the distinction of public vs. private may not actually matter quite as much in the context of IP ranges used on JEDI.
  • exikyut 5y ago
    That's awesome. I'm guessing you couldn't straightforwardly get port-forwards to individual machines though :)