[solved] ROS 6.1 NTP client does not update system clock

RouterOS General
1

Hello,
i am having trouble with NTP client after upgrade ( it worked at 5.24 )

some info

installed packages:

0 routeros-mipsbe 6.1
1 ipv6 6.1
2 routing 6.1
3 ppp 6.1
4 hotspot 6.1
5 security 6.1
6 dhcp 6.1
7 mpls 6.1
8 ntp 6.1
9 multicast 6.1
10 wireless 6.1
11 advanced-tools 6.1
12 system 6.1

routes:

0 ADS 0.0.0.0/0 78.83.80.1 0
1 ADC 78.83.80.0/20 78.83.84.250 ether1 0
2 ADC 192.168.80.0/24 192.168.80.1 ether2 0

ntp client info:

enabled: yes
mode: unicast
primary-ntp: 212.70.148.12
secondary-ntp: 94.236.192.26
dynamic-servers:
status: started

system clock:

time: 03:36:01
date: jan/01/2002
time-zone-name: Europe/Sofia
gmt-offset: +02:00
dst-active: no

thanks in advance :wink:

p.p i tested multiple ntp servers and still the same result.

RouterBoard RB750GL

2

Very interesting I had a similar problem when I upgraded to Ver6.0 using my NTP (131.173.17.20 - 131.173.17.7) which I had been using for years the clock would not sync - I am now using a local one and my pings times reduced down and pinging your Ntp addresses have the same ping times which I had before trying a new one?

My next question is would a slow NTP Client effect performance of routers which are slow to time sync?

MikroTik RouterOS 6.1 (c) 1999-2013 > http://www.mikrotik.com/


[admin@admin] > ping 212.70.148.12
HOST SIZE TTL TIME STATUS
212.70.148.12 56 237 81ms
212.70.148.12 56 237 118ms
212.70.148.12 56 237 94ms
212.70.148.12 56 237 107ms
212.70.148.12 56 237 153ms
212.70.148.12 56 237 100ms
212.70.148.12 56 237 84ms
212.70.148.12 56 237 115ms
212.70.148.12 56 237 93ms
212.70.148.12 56 237 81ms
sent=10 received=10 packet-loss=0% min-rtt=81ms avg-rtt=102ms max-rtt=153ms


[admin@admin] > ping 94.236.192.26
HOST SIZE TTL TIME STATUS
94.236.192.26 56 45 128ms
94.236.192.26 56 45 126ms
94.236.192.26 56 45 110ms
94.236.192.26 56 45 121ms
94.236.192.26 56 45 112ms
94.236.192.26 56 45 112ms
94.236.192.26 56 45 133ms
94.236.192.26 56 45 122ms
94.236.192.26 56 45 145ms
94.236.192.26 56 45 109ms
sent=10 received=10 packet-loss=0% min-rtt=109ms avg-rtt=121ms
max-rtt=145ms

[admin@admin] > ping 85.91.1.164
HOST SIZE TTL TIME STATUS
85.91.1.164 56 50 43ms
85.91.1.164 56 50 21ms
85.91.1.164 56 50 14ms
85.91.1.164 56 50 30ms
85.91.1.164 56 50 69ms
85.91.1.164 56 50 35ms
85.91.1.164 56 50 32ms
85.91.1.164 56 50 18ms
85.91.1.164 56 50 22ms
sent=9 received=9 packet-loss=0% min-rtt=14ms avg-rtt=31ms max-rtt=69ms

\

3 
ping 212.70.148.12
HOST                                     SIZE TTL TIME  STATUS                 
212.70.148.12                              56 252 4ms  
212.70.148.12                              56 252 4ms  
212.70.148.12                              56 252 4ms  
212.70.148.12                              56 252 4ms  
212.70.148.12                              56 252 4ms  
212.70.148.12                              56 252 4ms  
212.70.148.12                              56 252 4ms
  
ping 94.236.192.26 
HOST                                     SIZE TTL TIME  STATUS                 
94.236.192.26                              56  60 4ms  
94.236.192.26                              56  60 4ms  
94.236.192.26                              56  60 4ms  
94.236.192.26                              56  60 4ms  
94.236.192.26                              56  60 4ms

I don’t think 4ms is too slow, but thanks for your input.

4

4ms is very good - Is the clock still not updating and if not what does the logs say?

5

Yes its not updating, i even downgrade to ROS 5.25 and issue is still present. As for logs i can not see anything other than

system,info NTP params changed by cybertorture

Where can i find older version (5.24 prefferable)?

edit: Ok i found the source of the problem, i upgrade again to 6.1, than i llok at my firewall and i found out i m disabling 123 udp input ( strange thing is that it worked at ROS 5.24) now everithing is OK. Thanks for your time.

Cheers.

6

I am having the same problem after upgrading to 6.1. I am using a RB2011UAS as an AP only so no firewall installed.

What strange is that through Winbox the NTP client shows as stopped. But when I log into the CLI it show as started.

7

Actually if you do not use NTP as server, you can remove ntp package and use SNTP, it shows more info at very least. Hope that will help you. Cheers

8

Still having the same issue of ntp not synchronizing with ntp server.

I am using ROS 6.1Rc14, i wonder why it is not working
/system
[admin@MBJ] /system> ntp
[admin@MBJ] /system ntp> client
[admin@MBJ] /system ntp client> pr
enabled: yes
mode: unicast
primary-ntp: 196.25.1.1
secondary-ntp: 205.196.146.72
dynamic-servers:
status: started

After several time of restarting the time still stick at
/system> clock
[admin@MBJ] /system clock> pr
time: 21:48:03
date: jan/01/2002
time-zone-name: Africa/Lagos
gmt-offset: +01:00

Mikrotik did not say anything about the ntp package why it is not synchronizing. Plz any hep will be appreciated as it is affecting the users in hotspot and user manager.

thanks

9

Did you try to use other server?

10

Yes.

As you can see, the primary server is from south africa, while the secondary server i from US. Yet the ntp client is not synchronizing. Wen I ping the 2 ip they are replying.

What other way could i do for it to work.

Thanks