Cut down on relying on network time servers for synchronization!
Cut down on relying on network time servers for synchronization!
Sure, I didn't think about GPS much since I don't rely on it often (maps usually don't guide me to specific destinations anyway?). Still, it's a handy tool. I'm curious though—why doesn't GPS automatically sync your clock when you connect? It feels odd we use random time servers and rarely get asked. That kind of setup seems a bit unnecessary and raises some security concerns. Basically, just trust me on the clock, but for games and other apps, they often prompt whether to allow a connection, sometimes even without asking. I remember people using "atomic clocks" that got their timing from radio signals—it was pretty cool back then.
You might have misheard the speaker. Still, it seems like all devices should align with your router, even though no one actually does—each has its own time source. It’s a neat idea but not practical right now. 😅
Yeah Mark, your comment included a quote from Vishera, so I revised my post right away. Thanks for the NTP pool organization link @Zando_ Here are the details for the pool, and I’ll add it to the top post. I believed the numbers would be much higher, but globally there are 4,439 servers. This applies only to ntp pool .org. If we disabled time sync on things like virtual machine test systems, tablets, and smartphones, and only synced when absolutely necessary for safety or tracking criminals, imagine the reduced demand for these over 4,400 computers! There are at least two or three billion Windows PCs in use worldwide, with more likely. I’m confident more than 97% of those machines connect to the default windows.time.com NTP server. Who can say how much traffic NIST handles? If we all considered how often we sync our clocks and the method (offline vs network), I think it would greatly reduce our energy consumption from just this setting alone.
Precise timing is crucial for encryption to function correctly. Even a small discrepancy in your clock prevents secure connections from establishing. It’s more critical than simply adjusting the time with a kitchen timer. With a strong router, you can minimize usage by letting it act as both client and server for NTP synchronization—so your local network only needs to align with the router. On pfSense, I’ve set a rule to block LAN devices from accessing any servers other than themselves, which also prevents Windows from hardcoding its time source.
You're correct, I've seen this before too, but I don't agree with the "slightly off" assessment. It's not as strict as it seems. Try it yourself—shift your clock back two hours or two hours and forty-five minutes, and observe the results. I'm testing right now. I can still access sites like NASCAR, Leafly, and others without issues. Just leave it as is to support my claim. No problem, I just want to demonstrate it often works. It was 6:18, I set my clock to around 3, and everything functions fine. Give it a try! Your setup sounds impressive with the PFSense router, NTP redirection, and LAN synchronization—really solid!
It's frustrating dealing with Linux and Windows time discrepancies. The clocks always seem off by an hour after switching between systems. Starting from time servers makes sense because they mainly verify certificates, not exact local time. Adjusting your time slightly won’t affect their validity, but moving it significantly increases the chance of encountering problems where certificates expire or haven't started working yet.