NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NTP Issue - Time Jump
Hi all, Today for the second time since I've owned my OS 6 unit (now on 6.7.1 FW) the NTP process has incorrectly set my device time to a date in the past before correcting itself sometime later....
steveoelliott wrote:
May 30 09:23:34 DESPAIR connmand[5534]: ntp: adjust (jump): -454753305.317564 sec
Jan 01 00:01:49 DESPAIR systemd[1]: Time has been changed
Jan 01 00:18:53 DESPAIR connmand[5534]: ntp: adjust (jump): +454753299.218670 sec
May 30 09:40:33 DESPAIR systemd[1]: Time has been changed
I also use 0.pool.ntp.org, and the biggest NTP slew I see for 30 May is about 5 ms. I am wondering if something went south with the RTT estimate built into the protocol?
Thanks all...
I will say that the internet connection this device leverages is very slow circa 2Mbps but that should not be an issue for NTP and it's calculation. I will see how we get on with a new NTP server.
I understand that NTPD can be setup to reject huge time offsets and consider these erroneous / ignore them. I believe in future releases Netgear should configure it in this way to prevent this issue from occurring. It can cause all manor of issues.
steveoelliott wrote:
I believe in future releases Netgear should configure it in this way to prevent this issue from occurring. It can cause all manor of issues.
Sounds like a good idea. They might need some exclusion for the initial startup case, but that should be possible.
Your particular issue should be fixed in the 6.7.5-T299.
Yes... It is possible to make an exception if the NTP offset is high following a boot. There would be a valid reason for a large offset in this case.
I've messaged MDGM and Skywalker to ask if they can raise this as a bug / enhancement request for future releases.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
