This is strange. Everything you pasted looks fine. I am unable to reproduce the Reminder message through /opt/etc/init.d/S77ntpd or even "killall ntp" on the command line by itself.
I Have now killall ntp enabled and I have rebooted the router just 3 minutes ago.
I will wait for 15 minutes and check if the message is gone.
(* Reminder: The system time has not been synchronized with an NTP server.)
Router is up for 15 minutes now and the message doesn't disappear.
Maybe I have found the cause.
I followed the FAQ of : https://www.asus.com/support/FAQ/1037370 [Administration] How to set up Network Detection to make sure your router’s time zone synchronizes with NTP server?
Maybe I have found the cause.
I followed the FAQ of : https://www.asus.com/support/FAQ/1037370 [Administration] How to set up Network Detection to make sure your router’s time zone synchronizes with NTP server?
So I infer from the convoluted Asus FAQ that you were receiving a misleading message (clock not NTP synched) because you had not configured a not necessarily related function (WAN test).
I have been using a ping of my ISP's first hop router for WAN test.
on https://github.com/jackyaz/ntpdMerlin I would just remove the section under Usage in the readme that gives the path for non-entware users to start the script....and I could (should) probably be telling you this at that location to keep the signal-to-noise ratio higher here...
on https://github.com/jackyaz/ntpdMerlin I would just remove the section under Usage in the readme that gives the path for non-entware users to start the script....and I could (should) probably be telling you this at that location to keep the signal-to-noise ratio higher here...
Hello - Sorry for the NOOB questions, but to use an ntp pool, would I use your script file as is, or do I need to customize it for my network? For instance, I do not know about your use of 192.168.50.200 or the listen on br0. Also, how do you use the stats lines at the bottom of your script?
BTW, thanks Jack for an easy script. I just installed ntpdMerlin and it went without a hitch.
Hello - Sorry for the NOOB questions, but to use an ntp pool, would I use your script file as is, or do I need to customize it for my network? For instance, I do not know about your use of 192.168.50.200 or the listen on br0. Also, how do you use the stats lines at the bottom of your script?
BTW, thanks Jack for an easy script. I just installed ntpdMerlin and it went without a hitch.
The ntp.conf that ntpdMerlin provides if fine. This is a slightly different alternative.
Using "pool" instead of "server" only requires the slightly relaxed permissions of the "restrict source" line above
The iburst argument is generally recommend. It allows for quicker time synchronization at startup.
Using pool instead of server enables extra algorithms in NTPD which are considered to be good but I do not know the details
The DNS for pool.ntp.org is configured to return geographically close NTP servers. However, I have noticed that I sometimes get servers as far as 120 msec of delay away.
The default restrict permissions are intended to come into play if you provide NTP to the public, but will be in effect on your LAN as well
The localhost restrict permissions enable you to run all of the NTP commands without restriction
You may notice that, since I have a "server" at 192.168.50.200, it is on my LAN. I have another computer with an NTP daemon which has a GPS connected to it in order to provide better time. This ntp.conf line allows my router to take advantage of this as an NTP client. You would not include this line in your ntp.conf
The interface commands determine which networks you can provide NTP time to. The first line sets a default to not provide NTP time. The second line enables your router to provide NTP time on the LAN interface. Do you need "interface listen br0" for the router to have NTP time? No, it is only necessary if you want to provide NTP time to the computers on your LAN.
You do not need the stats. The router GUI graph data is collected another way. But if you are troubleshooting, it is nice for them to be available even if looking back and forth at the refererence documentation to decode is frustrating.
In order to validate NTP daemon startup, you need to first look at /tmp/syslog.log and then /opt/var/spool/ntp/ntp.log because it switches over
The leapfile can be considered esoteric but when they do happen it is nice to avoid the clock being instantaneously wrong by a second. You can wget the file at the URL in the comment.
Do not use minpoll or maxpoll below 6 (64 seconds) unless the target is your computer. If not your computer, do not set them at all.
Using "pool" instead of "server" only requires the slightly relaxed permissions of the "restrict source" line above
The iburst argument is generally recommend. It allows for quicker time synchronization at startup.
The default restrict permissions are intended to come into play if you provide NTP to the public, but will be in effect on your LAN as well
The localhost restrict permissions enable you to run all of the NTP commands without restriction
You may notice that, since I have a "server" at 192.168.50.200, it is on my LAN. I have another computer with an NTP daemon which has a GPS connected to it in order to provide better time. This ntp.conf line allows my router to take advantage of this as an NTP client. You would not include this line in your ntp.conf
The interface commands determine which networks you can provide NTP time to. The first line sets a default to not provide NTP time. The second line enables your router to provide NTP time on the LAN interface. Do you need "interface listen br0" for the router to have NTP time? No, it is only necessary if you want to provide NTP time to the computers on your LAN.
You do not need the stats. The router GUI graph data is collected another way. But if you are troubleshooting, it is nice for them to be available even if looking back and forth at the refererence documentation to decode is frustrating.
In order to validate NTP daemon startup, you need to first look at /tmp/syslog.log and then /opt/var/spool/ntp/ntp.log because it switches over
The leapfile can be considered esoteric but when they do happen it is nice to avoid the clock being instantaneously wrong by a second. You can wget the file at the URL in the comment.
Usually enabling stats is about writing them out to files or not. I can only assume that explicitly disabling stats in ntp.conf by @kvic was for the purpose of minimizing memory use, which would imply that stats would not run internally. I have not been able to find an answer to this in the reference documentation http://doc.ntp.org/current-stable/