トップに戻る

コメント (8)

tomassirio•1分前
Hey Jeff, I learn a lot through your content.

Thanks a lot for sharing knowledge!

Avamander•2時間前
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...

lightswitch05•3時間前
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?

Edit: I forgot to add, one of my favorite parts of being in the pool is basically a free uptime monitor of my ISP. There have been multiple cases where I see a blip in my offset then a full blown ISP outage within 78 hours of the blip, then a return to my normal offsets after to outage has resolved.

bityard•1時間前
I thought I remembered reading that they did not allow VPSes to be part of the pool because of the historical issues around VMs and timing, combined with the fact that the VPS operator could make host-level changes at any time that could impact the accuracy of the host. But now I'm not finding anything about that. Maybe they have enough monitoring and automation that running nptd on bare metal is not a strict requirement anymore?
omoikane•2時間前
> https://www.jeffgeerling.com/blog/2026/i-joined-the-ntp-pool...

I wonder why the wall clock on top is 10 seconds ahead of the bottom one?

zodwick•2時間前
One of those posts which truly hits you in the face and calls you an idiot for how much you don't know. Definitely a rabbit hole I'm going down this week. Thanks
jeffrallen•3時間前
PSA: The Swiss government has NTP servers on ntp{11,12,13}.metas.ch.

METAS is the Federal Institute of Metrology.

aaronax•3時間前
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?