Who is responsible for managing your unit’s IP space? Is it you? Is it the 255A or 53? Do you actually have someone who is responsible for issuing and controlling the IP space for the unit? There was a recent discussion in the 255N Facebook group about things we can do to secure the network. One of the things brought up was knowing every device that was on the network. While that is important (and one I will get too shortly), today I want to talk about something a little simpler, knowing where all of your IP space is.
So if you happened to be up and in system a couple of weeks ago, you may have noticed a prolonged period of “disruption”. The brigade on rotation here began to see instability across the satellite network effecting both TDMA and FDMA. We were eventually informed by the commercial satellite provider that the problem terminal was indeed located in the Fort Irwin area. The focus of this post is sort of an AAR of what occurred in an effort to identify the responsible terminal, and what could have been done to improve the situation from the very beginning and to minimize the chances of this happening again.
On this day in 2008, I learned the very hard lesson that how well we prepare our Soldiers to do their jobs in combat can mean the difference between the life and death of others.