so...I put a Time Server in my HomeLab

About this video

Chuck installs a self-hosted time server in his studio using Timebeat’s Open Timecard Mini, a PCIe card combining a Raspberry Pi CM4 server with a GPS/GNSS module that receives time from satellites carrying atomic clocks. The video first gives a rapid history of timekeeping from sundials to quartz and atomic clocks, then explains why computers drift: a quartz real-time clock vibrating 32,768 times per second, kept alive when powered off by the CMOS battery, can drift roughly one to two seconds per day due to temperature, imperfections, and aging. NTP fixes this by polling a server on UDP port 123, with stratum levels measuring distance from an atomic-clock source, delivering about one to ten milliseconds of accuracy. PTP, the Precision Time Protocol, goes far further using hardware timestamping at the NIC, a grandmaster clock chosen as the most accurate source, and optional boundary and transparent clocks in switches, reaching nanosecond accuracy. The build is not smooth: the GPS antenna gets no satellite lock inside the server room or studio, showing a clock stuck at 1970, and only works once placed outside. After configuring Timebeat’s YAML, starting the service, and watching offsets fall in its Elasticsearch/Grafana monitoring, he sets up a client server, fixes a firewall block by allowing UDP ports 319 and 320, enables hardware timestamping, and reaches nanosecond sync. He also runs Chrony so non-PTP systems can use his own stratum-one NTP server. Real demand, he notes, comes from financial trading, NASA, and broadcast.

Key takeaways

• A computer’s quartz RTC drifts about one to two seconds a day, which is why systems must regularly sync to an external time source
• NTP uses a stratum hierarchy based on distance from an atomic clock and gives roughly millisecond accuracy; Windows defaults to the stratum-two time.windows.com
• PTP achieves nanosecond accuracy through hardware timestamping at the NIC and a grandmaster clock, with boundary and transparent clocks helping distribute time
• GPS reception is the fragile part of the build: the antenna got no satellite lock indoors and the clock sat at 1970 until the antenna was moved outside
• On the client side, sync initially failed on a firewall rule; allowing UDP ports 319 and 320 and enabling hardware timestamping got the server to nanosecond sync

Episode details: published October 8, 2024 · 28:25 long. Summary written by Self Growth Videos from the episode itself. Business results and any income figures mentioned are NetworkChuck’s own claims, shared for education — they are not typical or guaranteed.

← Previous: 18 Weird and Wonderful ways I use Docker · Next: your home automation SUCKS!! →

All NetworkChuck videos · NetworkChuck profile · NetworkChuck on YouTube