"large amounts of data could provide several benefits for those in a position to collect and analyze it for threat intelligence and other purposes"
Another great example of computer literacy in the world of journalism.
Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
81–90 of 257 posts
Re: Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
#82Earlier quoted context omitted.
Some of those less-cluefull operators include Juniper and Azure[1], Cisco[2][3], and probably many other companies. When Cloudflare put its 1.1.1.1 DNS server into use, it started receiving huge amounts of packets destined to unroutable addresses because the 1.0.0.0/8 space was (mostly?) unused. If you configure your routers correctly, none of these IP addresses should resolve, anyway. If something in your network is…
I know of a couple companies that used 1.0.0.0/8 as their internal VPN/WAN network. Myself and others explained why this could be problematic but we were ignored. It's actually mostly fine as long as you 1) never need to reach that network and 2) block traffic in that network from leaving your edge network and 3) triple-check that you have blocked that network from ever being announced from your routers. Downside bei…
T-Mobile used or uses UK MoD space also for NAT.
Re: Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
#83"several Chinese companies use network numbering systems that resemble the U.S. military’s IP addresses in their internal systems" I don't think I've heard of this before. What does it mean? Does China operate a disconnected BGP network? Or do they have some modified protocol, or what?
Alibaba for example use DoD address ranges for their management servers running Alicloud services. They assumed since nothing in their cloud platform would connect to those addresses they can use these them to alleviate IPv4 shortage. In Alicloud, the customer have the right to use any RFC1918 addresses, so they had to be creative since they didn’t have sufficient IPv4 addresses.
Re: Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
#84Earlier quoted context omitted.
What IPs does the DoD actually host defense-related services on? E.g. https://www.defense.gov/Resources/Military-Departments/A-Z-L...
NIPR and SIPR don't talk to the global routing tables for v4 and v6. Generally if a DOD person needs to access commercial internet resources for things, it'll be through a separate commercial network purpose LAN, or through something like an rdp session to a Citrix thin client to do that.
I think you'd be surprised. Most NIPR computers just use a regular proxy server for internet access. But example: 214 /8 is a DoD owned block, and "weather.af.mil" is on that block, and both externally and internally reachable.
Re: Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
#85Earlier quoted context omitted.
how would nat help in this case?
If they're not actually using the whole /8 (highly likely), you can setup a 1:1 NAT. basically from network b, if you want to talk to network a, you find out the address in 11/8 that corresponds to the 10/8 address and vice versa. You can use split horizon dns to make it mostly transparent. Every networking problem in the world can be solved with more NAT or more encapsulation :)
You don't have to use every address in 10.0.0.0/8 to effectively fill it up. If your corporate policy is to assign a /16 to each floor of a building, and you have a LOT of buildings it's pretty easy to fill up the space even if most of the /16s are sparsely populated. It's much easier to move on to the 11. space when you build that new building that pushes you over than renumbering your entire corporate LAN.
Re: Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
#86Earlier quoted context omitted.
These IP addresses were unused for a very long time, so using them on internal networks worked fine. Once the Floridian company in the article started announcing them, gateway routers on the Chinese internal networks may have started sending their traffic to Florida.
Why would you do that though when there are perfectly fine internal address ranges available?
[deleted]
Re: Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
#87This is a complete side point, but what does this sentence mean? > Created in 2015, the DDS operates a Silicon Valley-like office within the Pentagon.
The first paragraph a job description gives some context to their culture:
> How do you feel about the cloud? Specifically, what are your thoughts on the cumulus clouds of Bespin? Do you believe Cloud City is composed of only cumulus clouds? Do you have any idea about what we are asking? If your answer is yes, definitely read on. If no, still read on, but we might find your lack of faith disturbing!
Re: Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
#88Earlier quoted context omitted.
Thanks a lot, Appreciate. It is not I don't want to pay the washingtonpost.com. I just don't have time to read them.
I've tried subscribing to a few news sources, including WaPo, but I can't handle the political agendas (right, left, or any of it). I've had better luck with subscription based aggregators, but nothing exciting enough to want to plug one in particular. Always looking for new options to try.
I think the key question isn't which political agenda they have, but whether they report facts or opinions.
In that regard, WaPo is pretty good but you can still do better: https://www.adfontesmedia.com/static-mbc/
Re: Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
#89Earlier quoted context omitted.
NIPR and SIPR don't talk to the global routing tables for v4 and v6. Generally if a DOD person needs to access commercial internet resources for things, it'll be through a separate commercial network purpose LAN, or through something like an rdp session to a Citrix thin client to do that.
I think you'd be surprised. Most NIPR computers just use a regular proxy server for internet access. But example: 214 /8 is a DoD owned block, and "weather.af.mil" is on that block, and both externally and internally reachable.
Not that NIPR computers don't have access to the internet - but because this isn't 1987, those individual workstations would never have public facing DoD v4 IPs. They'll always be behind some combination of NAT and firewall or as you mentioned, proxy. Certainly there could be some DoD public IP on the external interfaces of said firewalls. If I had to guess very often the public facing side of those boxes might be a commercially acquired local ISP using that ISP's IP space, and not actual DoD IP space...
Re: Millions of the Pentagon’s dormant IP addresses sprang to life on January 20
#90Earlier quoted context omitted.
Why would you do that though when there are perfectly fine internal address ranges available?
I suspect there are a decent number of network engineers who think it's funny to use DoD IPs for their internal network, especially given what their logging system will probably tell them by default. If you drive around with a WiFi stumbler running, you'll run into networks with names like "UTAH DATA CENTER" and "SIPRnet", etc for the same reason.
I always hated seeing “FBI Surveillance Van”
Made me wanna climb out of my FBI Surveillance Van and have a word with them.