I joined the NTP Pool, but not with my Stratum 1 Pi
41 points by fortran77 3 hours ago | 8 comments

Avamander 10 minutes ago
For the price and complexity of building a good Linux-based time server I'd heavily recommend looking at FPGA-based solutions instead. x86 platforms also have PCIe PTM and TGPIO options available[0], which are tad better than the common ARM equivalents and GPIO interrupts.

In general Pi-s are relatively bad for timekeeping. Not just the NIC (which can be replaced by hats with their own), there are also oscillator replacement mods[2] to work around this to some extent. Though all this still leaves many other sources of timekeeping error.

So if the goal is low-cost precise timekeeping, one can assemble something FPGA-based[2] for quite a bit less money, that can reach very low noise figures. You can spend the remaining money on the GNSS antenna and receiver instead.

I'm also sure a FPGA-based approach could be taken even further with some external timekeeping chips available and the FPGA could just do the NTP/PTP protocol stuff.

[0]: https://www.youtube.com/watch?v=zxK0_j2Ah2I [1]: https://raspberrypi.stackexchange.com/questions/74482/switch... [2]: https://fy.chalmers.se/~f96hajo/fakernet/board_Arty_A7-35-GP...

reply
lightswitch05 48 minutes ago
Great write up! I too run a stratum 1 and am part of the pool. Except, I have way less interesting hardware. One benefit on going cheap is having multiple stratum 1s then you can have some redundancy and have more interesting local peers to compare results against. I do see a more expensive setup in my future, though.

Anyways, I use NTPSec- which is the default these days on Debian when you apt-get install NTP. I’ve not tried Chrony, but I see it mentioned all the time.

I’m curious what others here are running and their thoughts on the pros and cons?

reply
Palomides 33 minutes ago
I think most people run chrony or ntpd-rs; not part of the pool, but I've been using chrony for a while, and it seems like ntpd-rs's support for PTP (which I "need") is still under development
reply
geerlingguy 39 minutes ago
In the NTP Pool community, I've seen a few people mention CenterClick NTP servers; I'm happy to do my own DIY builds (Pi or otherwise), but this looks like a nice option for SMBs or time-nuts who don't want to manage their own hardware: https://centerclick.com/ntp/

There are also a lot of people who buy old Spectracom or other 'enterprise' time servers since they can be had for low hundreds of dollars with some nice features like rubidium or OCXO oscillators, so they can hold over time much more accurately when GPS is down, or upstream NTP providers are unreachable.

And regarding chrony, it's the default in many distros now, I like some of its built-in monitoring and clock adjustments, it just feels easier to manage if you want more than just base NTP features. It also supports hardware timestamping if you have network hardware that has it, which IIRC NTPd doesn't? I haven't messed with systemd-timesyncd or ntpd-rs, so can't say much on them.

reply
nahikoa 39 minutes ago
Some of the cool kids are moving to https://github.com/pendulum-project/ntpd-rs
reply
aaronax 40 minutes ago
What speed did you choose in the pool dashboard? How many request per second are you serving, and do you have a goal for that?
reply
geerlingguy 33 minutes ago
I started at 25 Mbit to see how things would go, and found the Oxtrys VPS I have the public server running on could handle that without issue.

Over the past few weeks I bumped it up to 50, then 100, and now it's at 250 Mbit. At 100 Mbit I was seeing 180-250 requests/sec. At 250 (just switched earlier this morning) I'm seeing 500-600 requests/sec.

I'm monitoring things on the server with chronytop[1], a tool I whipped up with Claude since I didn't see any other concise dashboards and hated `watch`ing chronyc sources to get any kind of updated data.

[1] https://github.com/geerlingguy/chronytop

reply
jeffrallen 40 minutes ago
PSA: The Swiss government has NTP servers on ntp{11,12,13}.metas.ch.

METAS is the Federal Institute of Metrology.

reply