Hello
When I install the ntp package, the ntp-client does not work.
If I disable the ntp package and use the ntp client built into RouterOS (5.14), the time is updated correctly.
I use the same ntp servers in both cases.
Have anyone else had the same problem?
Can you post /system ntp client export
The working /system ntp client on the built-in ntp
[admin@xyz] > system ntp client export
# jan/02/1970 01:01:03 by RouterOS 5.14
# software id = IPS6-N1JY
#
/system ntp client
set enabled=yes mode=unicast primary-ntp=79.136.87.162 secondary-ntp=193.11.185.39
[admin@xyz] > /system ntp client print
enabled: yes
mode: unicast
primary-ntp: 79.136.87.162
secondary-ntp: 193.11.185.39
poll-interval: 16s
active-server: 79.136.87.162
last-bad-packet-from: 192.168.112.199
last-bad-packet-before: 5h33m36s610ms
last-bad-packet-reason: zero-transmit-timestamp
On the non-working ntp in the ntp 5.14 packet
[admin@xyz] > /system ntp client export
# jan/01/2002 02:00:59 by RouterOS 5.14
# software id = IPS6-N1JY
#
/system ntp client
set enabled=yes mode=unicast primary-ntp=79.136.87.162 secondary-ntp=193.11.185.39
[admin@xyz] > /system ntp client print
enabled: yes
mode: unicast
primary-ntp: 79.136.87.162
secondary-ntp: 193.11.185.39
status: started
>
Hello
I just upgraded to the newly released RouterOS 5.15 and here the built in NTP client does not update my clock.
It seems that it gets in contact with the NTP server but the system clock isn’t updated.
I use the same settings as before.
[admin@xyz] /system ntp client> /system ntp client export
# jan/02/1970 01:10:00 by RouterOS 5.15
# software id = IPS6-N1JY
#
/system ntp client
set enabled=yes mode=unicast primary-ntp=79.136.87.162 secondary-ntp=\
193.11.185.39
[admin@xyz] /system ntp client> /system ntp client print
enabled: yes
mode: unicast
primary-ntp: 79.136.87.162
secondary-ntp: 193.11.185.39
poll-interval: 16s
active-server: 79.136.87.162
What’s going on?
When i upgraded to 5.15 I did it by uploading the package routeros-mipsbe-5.15.npk to RB and rebooted.
Then I extracted the ntp-5.15-mipsbe.npk from the all_packages-5.15.zip file, uploaded to RB and rebooted.
Is this the proper way of using the ntp package, or shall I take all packages that i need from the all_packages-5.15.zip file instead so I dont mix.
…because the ntp client does not work for me after doing this.
i have same problem with 5.15 on rb1100
i user all packages for upgrade and know my NTP client is not working
the status is reached but never synchronize
how can i downgrade ntp client package ?!
thnks
that is proper way to do that.
Also, you can check with other ntp server, i checked on mipsbe 5.15 and ppc - both synchronized without problems.
I have tested a couple of different NTP servers form the pool.ntp.org and some other.
None of them worked. Neither using the ntp client in the system package, nor by the ntp-5.15-mipsbe.npk package.
Though, I can see that /system clock is set to 1970 when I use the system packaged ntp client and its set to 2002 when I use the ntp-5.15-mipsbe.npk package.
Using the the ntp-5.15-mipsbe.npk package, I just have status=started. It never changes from there.
OK. I just downgraded to 5.14 and my problem remains.
So, how do I figure out what the problem is?
Does anyone have an idea?
Just for fun, can you extract the configuration of the ntp server part too? /system ntp server print
I may recall some MT guy saying that ntp client without ntp package is a sntp client, and plain ntp client within ntp package.
Tried the new 5.16 and it still does not work.
Of course I can post my server part (using the ntp package)
/system ntp server print
enabled: no
broadcast: no
multicast: no
manycast: yes
broadcast-addresses:
But as I don’t use it (as the clock isn’t synchronized) it won’t do anything.
The client looks like this
/system ntp client print
enabled: yes
mode: unicast
primary-ntp: 178.78.255.254
secondary-ntp: 83.177.160.188
dynamic-servers:
status: started
I just used the same settings and it worked for me. Do you have any sort of firewall on your router possibly blocking the NTP traffic?
[admin@MikroTik] /system ntp server> print
enabled: no
broadcast: no
multicast: no
manycast: yes
broadcast-addresses:
[admin@MikroTik] /system ntp server> .. cl
[admin@MikroTik] /system ntp client> print
enabled: yes
mode: unicast
primary-ntp: 178.78.255.254
secondary-ntp: 83.177.160.188
dynamic-servers:
status: synchronized
I’ve asked my ISP. No answers yet. They claim not to block on their FAQ but I asked any way.
The RouterBoard is connected directly to my CPS.
I’ve caught the network communication using Wireshark and NTP packages leaves the RB, but no replies can be seen.
I’ve come to a conclution that I don’t understand.
If I place a switch between my RouterBoard and my CPS, the NTP client don’t synchronize.
If I connect my RouterBoard directly to my CPS, the NTP synchronizes.
With the switch in between all other communication works as expected.
Can anyone explain to me why this happens?
I found the cause.
I upgraded the firmware of my switch and after that the NTP synchronizes nicely in my setup.
Firmware bug in a switch… I’ve not bumped into that before.
I haven’t heard of that before either.
I got the NTP server’s Client part workign by switching NTP servers around.
Then when I tried to use it as a NTP server -the client says “server not synchronised”
5.19 x86 and mipsbe
Same thing, 5.19 x86, mipsbe and powerpc platforms DON’T synchronize their time with NTP server. Worked correctly on 5.18 before upgrading to 5.19 on all platforms.
Actually this was not the root cause. The NTP client stopped working after a while…
Same issue here. I also noticed that my scripts aren’t working any more after the update.