Introduction
In enterprise infrastructure maintenance, “close enough” is an invitation for systemic drift. When designing isolated, high-security surveillance and critical system environments, relying on standard pool NTP servers over an unstable wide-area network (WAN) is a structural vulnerability. If the network drops or experiences high jitter, your local systems drift, shattering log atomicity and corrupting event timelines during cross-examination.
This post documents the forensic implementation of an air-gapped, out-of-band Network Time Protocol (NTP) server built to lock onto direct orbital satellite arrays, operating completely independent of an internet connection.
The Architectural Challenge: The Isolated Perimeter
We were tasked with stabilizing time synchronization for an air-gapped network site running an expansive surveillance array. Standard public stratum servers were unavailable due to strict firewall policies blocking outbound ports.
If a security event occurred, the sub-second variance between separate camera streams and access control logs could make cross-referencing logs mathematically impossible. We needed a local Stratum 1 time provider on-site.
Engineering Phase 1: Physical Telemetry & Geospatial Mapping
To bridge the gap between orbital atomic clocks and our local rack-mounted servers, we deployed a dedicated GPS/GNSS receiver antenna.
Standard installation manuals suggest simply placing the receiver “near a window.” In a high-interference environment, that is a recipe for multipath propagation errors. We had to calculate exact physical telemetry parameters to avoid structural signal bouncing:
Geospatial Coordinate Locking: We manually mapped the precise latitude and longitude coordinates of the physical mounting bracket down to six decimal places.
Elevation Analysis: We calculated the absolute height above mean sea level (AMSL) to optimize the receiver’s geometric dilution of precision (GDOP).
By feeding these precise telemetry coordinates into our hardware controller, we allowed the receiver to bypass the standard, time-consuming blind sky search of upto 72hrs. It immediately locked onto the exactsatellite vector coordinates expected in our horizon grid.
Engineering Phase 2: Terminating the Physical Layer
The next bottleneck was the physical run. We deployed a shielded coax cable from the roof assembly down to the data closet.
[Orbital Satellites]
│
│ (Direct Line of Sight)
▼
[GPS/GNSS Antenna] (Roof Mounted / Calculated Elevation)
│
│ (Shielded Low-Loss Coaxial Cable Run)
▼
[Stratum 1 NTP Appliance] (Data Closet Rack)
│
│ (Isolated LAN / Category 6 Ethernet)
▼
[Surveillance & Core Network Infrastructure]
When terminating high-frequency telemetry lines, bend radiuses matter. A single sharp kink can alter the cable’s impedance, causing signal reflection and packet drops. We routed the cable through dedicated conduit, maintaining a strict 10x diameter bend radius, and terminated it cleanly into our Stratum 1 hardware clock module.
Engineering Phase 3: Validating Stratum 1 Convergence
With the hardware locked onto 4+ stable satellites, we updated our core switch and server configurations to point to our new local out-of-band IP.
Using diagnostic polling utilities, we verified the jitter dropped to less than $1 \text{ ms}$, with an offset hovering at near-zero parameters:
remote refid st t when poll reach delay offset jitter
===================================================
*GPS_RECEIVER .GPS. 0 l 4 16 377 0.000 0.012 0.004Lessons From the Field
Never Trust Automatic Telemetry: Manually injecting your local coordinates and elevation reduces satellite convergence times from 45 minutes down to seconds.
Physical Integrity Dictates Logical Performance: A perfectly configured NTP daemon means nothing if your physical coaxial shielding isn’t properly grounded to eliminate ambient RF noise from nearby high-voltage lines.