Actually, it's the opposite. Prior to V15, the ntp update code was bugged such that it never fired again after the router was booted and set the time.
Just to make sure, try setting the router to log successful updates via telnet/ssh with
reboot not necessary after changing this setting.Code:nvram set ntp_log=1 nvram commit
Then you should see entries like this in the syslog
Code:Dec 3 05:59:57 ntp: start NTP update Dec 3 05:59:57 ntp: NTP update successful after 1 attempt(s)
For me, it's been very accurate. I have a PC that I'm using with Windows Media Center as my main home theater that has a RTC that runs a bit fast. I'm using the router as my network SNTP server to update it's clock and it's kept things right in sync (comparing the PC clock with the clock on my cable box that I still have)
I may also re-think the default logging setting for the next release.
Thanks John !
Now I can see the successful NTP update in the logs.
But I still wonder why the router had a 7 seconds difference, especially if NTP is working better now.
Anyway .. I will check for time differences in a few days/weeks again.
Regards