Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon May 23, 2022 8:39 Post subject:
Please note....
The syslog now prints the delta offset on NTP update, the delta offset is expressed in milliseconds.
When you first reboot the router e.g. after a FW upgrade and goto syslog.
The first delta offset after the initial NTP update is crap, because the syslog date at that time is counting from 1970, so you will a total bullshit delta.
The subsequent NTP updates depending on the interval set will have a realistic delta offset. Remember most routers dont have internal RTC and heavy CPU loads can cause the software clock to drift more.
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Mon May 23, 2022 8:48 Post subject:
the-joker wrote:
Please note....
The syslog now prints the delta offset on NTP update, the delta offset is expressed in milliseconds.
When you first reboot the router e.g. after a FW upgrade and goto syslog.
The first delta offset after the initial NTP update is crap, because the syslog date at that time is counting from 1970, so you will a total bullshit delta.
The subsequent NTP updates depending on the interval set will have a realistic delta offset. Remember most routers dont have internal RTC and heavy CPU loads can cause the software clock to drift more.
Please use that realistic drift delta offset to determine the ideal drift vs interval and adjust the interval to suit your most desired outcome.
Here was part of my syslog right after firmware upgrade reboot:
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon May 23, 2022 8:53 Post subject:
That doesnt show anything delta related
youre looking for something like
daemon.info process_monitor[1716]: Local timer delta is 1653237546 for instance of an initial bullshit value counting from 1970 or whatever, a realistic value for me after 12 hours interval is daemon.info process_monitor[1716]: Local timer delta is 0
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Mon May 23, 2022 8:58 Post subject:
the-joker wrote:
That doesnt show anything delta related
youre looking for something like
daemon.info process_monitor[1716]: Local timer delta is 1653237546 for instance of an initial bullshit value counting from 1970 or whatever, a realistic value for me after 12 hours interval is daemon.info process_monitor[1716]: Local timer delta is 0
So the NTP interval is incrementing by additional 12 hours, until I find the delta is no longer acceptable.
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Mon May 23, 2022 12:10 Post subject:
the-joker wrote:
That doesnt show anything delta related
youre looking for something like
daemon.info process_monitor[1716]: Local timer delta is 1653237546 for instance of an initial bullshit value counting from 1970 or whatever, a realistic value for me after 12 hours interval is daemon.info process_monitor[1716]: Local timer delta is 0
So the NTP interval is incrementing by additional 12 hours, until I find the delta is no longer acceptable.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon May 23, 2022 12:32 Post subject:
mwchang wrote:
the-joker wrote:
Yep, lets see what it says in 48 hours or 172800 seconds.
I turn off everything electronic when going to sleep or leaving home. SO let others help you out...
Anyway, will have a look at the log again before turning off my router....
If thats true your ntp interval only needs to be 12 hours or 15 hours max. there's no point setting 48 hours interval otherwise if you shut everything off at night.
When router starts up or reboots regardless of ntp interval set it will update ntp and then only re-update on the interval set. this makes your choices more confounding with respect to your practices (commendable energy saving choices)
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Mon May 23, 2022 16:44 Post subject:
the-joker wrote:
If thats true your ntp interval only needs to be 12 hours or 15 hours max. there's no point setting 48 hours interval otherwise if you shut everything off at night.
When router starts up or reboots regardless of ntp interval set it will update ntp and then only re-update on the interval set. this makes your choices more confounding with respect to your practices (commendable energy saving choices)
You are essentially only under normal circumstances updating ntp once in 24 hours.
Thank you for the tip!
The log didn't change much related to time, turning the router off... Good night (HKT)!
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
But it's used only when the Server IP/Name (nvram show ntp_server) is blank!!
And this behavior is also related to DNScrypt. I am wondering whether Unbound should be checked because it also requires a correct clock to work. That should be (nvram get recursive_dns)!