Community discussions

MikroTik App
 
bd5ive
just joined
Topic Author
Posts: 7
Joined: Tue Jul 12, 2011 9:28 pm

ntp client not working after upgrade to version 6.40.4

Mon Oct 16, 2017 12:05 pm

NTP Client Stops syncing after upgrade to 6.40 from 6.38 on my RB1100AHx4
had to be sure so updated another device (RB751U-2hnd) same results, was working fine before.
on 751 after upgrade it showed synchronizing but after disable/enable it just shows started but never syncing.
used almost 20 different time servers, still same results.
here is my export :
/system ntp client
set enabled=yes primary-ntp=216.239.35.4 secondary-ntp=216.239.35.8
and the results:
[administrator@TSF_Maintik] > sys ntp cl pr    
          enabled: yes
             mode: unicast
      primary-ntp: 216.239.35.4
    secondary-ntp: 216.239.35.8
  dynamic-servers: 
           status: started
 
sihubert
just joined
Posts: 9
Joined: Wed Feb 13, 2019 1:22 pm

Re: ntp client not working after upgrade to version 6.40.4

Wed Jul 03, 2019 11:09 am

Hi,
Any update on this? I have the same issue on ROS 6.43.12.
Thx in advance.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 13186
Joined: Thu Mar 03, 2016 10:23 pm

Re: ntp client not working after upgrade to version 6.40.4

Wed Jul 03, 2019 3:24 pm

Does your router (the router itself, that's important) have connectivity with NTP servers? You can check it by running /tool traceroute 216.239.35.4 count=1. Do you have any firewall filter (or raw or ...) rules which might block UDP port 123 on chain=input or chain=output? Do you have fw rule similar to
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
?
 
sihubert
just joined
Posts: 9
Joined: Wed Feb 13, 2019 1:22 pm

Re: ntp client not working after upgrade to version 6.40.4

Wed Jul 03, 2019 4:46 pm

Funny, I just figured out the problem, and you're absolutely right :
Does your router (the router itself, that's important) have connectivity with NTP servers?
was the issue. The router missed a route, and I was dumb enough to ping and trace NTP servers from my laptop and not from the router directly... Just added a routing policy on the router and it synchronized instantly.

BTW, part of the original problem was that this specific router is a NTP client (of Web NTP servers), and also a NTP server for other nodes in the private network. When the router was not synchronized, it sent NTP replies to the private nodes with an "unsynchronized" flag, so that the nodes ignored the packets. Thus the private nodes did not sync as well.

So as a note for myself, always check the whole NTP synchronization chain, because if a node does not synchonize, maybe that's because its server is not synchronized... and so on.