In ROS v 6, I used the SNTP client to set the system clock in all my devices. I've upgraded my home network to V 7.4, and can't seem to get the clock to sync with any NTP servers. The SNTP tab in Winbox is missing, and Setting up the NTP client is also not working. I disabled the NTP client and enabled the IP/Cloud time setting function. Am I doing something wrong? Should I trust the IP/Cloud functions?
Thanks in advance for any help or suggestions.
Re: Setting System Clock
Just checked, nothing wrong with SNTP client on my Hex, ROS7.4, Winbox 3.37.
Which version of Winbox are you using ?
Since you say it's not visible in Winbox, which terminal command did you use and how did you determine it was not working ?
Conceptually there is nothing wrong with time settings in IP/Cloud, worst case it's not as accurate as you like or want.
Which version of Winbox are you using ?
Since you say it's not visible in Winbox, which terminal command did you use and how did you determine it was not working ?
Conceptually there is nothing wrong with time settings in IP/Cloud, worst case it's not as accurate as you like or want.
-
-
davidreaton
Frequent Visitor
- Posts: 88
- Joined:
Re: Setting System Clock
I'm using WinBox 3.37. I'm not at the command line. I don't see the SNTP option under the system tab in WinBox. I thought maybe it was now not in the basic install package. At the system terminal, under /system, there was no sntp option available. I'll stick with the ip/cloud option for now. It seems to work. But, I'd still like to understand this.
Thanks for the response.
Thanks for the response.
Re: Setting System Clock
SNTP is killed...
now is NTP Client and NTP Server.
Do you not see that options????? Both on terminal and winbox
now is NTP Client and NTP Server.
Do you not see that options????? Both on terminal and winbox
Code: Select all
/system ntp client
set enabled=yes
/system ntp server
set enabled=yes
/system ntp client servers
add address=193.204.114.232
add address=193.204.114.233
Re: Setting System Clock
My mistake. I use both names for the same.SNTP is killed...
now is NTP Client and NTP Server.
-
-
davidreaton
Frequent Visitor
- Posts: 88
- Joined:
Re: Setting System Clock
Yes, I saw the NTP client in Winbox, and after ROS 7 upgrade on my RB4011, it defaulted to multicast / pool/ntp.org / VRF main. This did not work for me. Other devices (CAP XL and RB962), after the V 7 upgrade, defaulted to UNICAST / pool.ntp.org / VRF main, and this DID work well. The difference was Multicast vs Unicast, and I'm not sure what this specifically means for the NTP client. I'm going to switch the RB 4011 away from IP/Cloud and change the multicast to Unicast and see if it works.
Thanks for the help and answers and for relieving me of a bit of ignorance.
Thanks for the help and answers and for relieving me of a bit of ignorance.
Re: Setting System Clock
Multicast was intended to work everywhere, and with intentional effort by all network owners between the endpoints it can be made to do so, but as a rule, multicast doesn’t work over the Internet because you can’t ever get that many ducks in a row.