configuration looks fine. the NTP client doesn’t give any detailed status, uninstall the NTP package if you are not using it as a NTP server, and you will get SNTP client, which gives better status info:
You didn’t give much information about how your router is set up, but if you are using it as an AP within a local subnet you could be missing a default route or default gateway. Another possibility is firewall filter rules that are interfering.
I don’t think this has anything to do with NTP but I think the second DNS should be 208.67.220.220
/ip dns
set allow-remote-requests=no cache-max-ttl=1w cache-size=2048KiB \
max-udp-packet-size=512 servers=208.67.222.222,208.67.222.220
I also wonder why the network address doesn’t match the IP address for the BigPon Interface. The use of interface=BigPon / actual-interface=BigPond suggests that something is configured in a way that I can’t follow.
/ip address print detail
Flags: X - disabled, I - invalid, D - dynamic
0 address=192.168.88.1/24 network=192.168.88.0 interface=ether1
actual-interface=ether1
1 D address=58.165.11.141/32 network=10.112.112.125 interface=BigPon
actual-interface=BigPond
I don’t know the details of how bigpond is set up but the address / network on the bigpond interface looks ‘wrong’ - Normally the address wouldn’t be a /32 but /29 or lower and the network would tally with the interface IP address.
Can’t you use DHCP on the internet facing address?
Can users on the LAN get to the Internet?
Can you ping www.yahoo.com or an internet IP address from the mikrotik?
It’s a PPP connection - they hand out /32s, and the network address/broadcast address/gateway can be on entirely unrelated interfaces. With a /32 the IP information is irrelevant since it’s just a host address, the interface itself becomes the gateway.
Looks like the NTP server being used might be ‘dead’ - as suggested earlier try another pair from pool.ntp.org - if you use nslookup you should get the list of servers…
i have this script scheduled once in month or two:
# ROS V5.5
# once in some time lets use some other NTP servers
# pick your country code (but not all works):
:local region "us"
:local ntp1 [:resolve ("0.".$region.".pool.ntp.org")]
:local ntp2 [:resolve ("1.".$region.".pool.ntp.org")]
/system ntp client set primary-ntp=$ntp1 secondary-ntp=$ntp2
:log info ("NTP servers updated, ".$ntp1.", ".$ntp2)
Based on the information you provided, it appears that you have correctly configured the NTP client on your router with the primary and secondary NTP servers set to 67.215.65.132, and a polling interval of 16 seconds. However, you mentioned that the time on the router never updates.
One thing you may want to check is if the NTP servers 67.215.65.132 are reachable and responding to NTP requests from your router. You can try pinging the NTP servers or using an NTP client tool to verify their availability. If the servers are not responding, you may need to update the NTP server addresses to valid and reachable NTP servers.
Additionally, make sure that the NTP client is enabled and running on your router. You can check the status of the NTP client using the “/system ntp client print” command to ensure that it is enabled and configured correctly or light is on