Hi,
For some reason my ntpd doesn't get any replies from the time servers.
They can however be pinged, so I'm unsure what causes this. Any ideas?
Thanks!
Max
$ doas ntpctl -s all
0/4 peers valid, constraint offset 107s, clock unsynced
peer
wt tl st next poll offset delay jitter
203.159.70.33 from pool pool.ntp.org
1 2 - 215s 300s ---- peer not valid ----
203.158.118.2 from pool pool.ntp.org
1 2 - 215s 300s ---- peer not valid ----
203.158.247.150 from pool pool.ntp.org
1 2 - 215s 300s ---- peer not valid ----
124.109.2.169 from pool pool.ntp.org
1 2 - 215s 300s ---- peer not valid ----
$ ping 203.159.70.33
PING 203.159.70.33 (203.159.70.33): 56 data bytes
64 bytes from 203.159.70.33: icmp_seq=0 ttl=254 time=34.143 ms
64 bytes from 203.159.70.33: icmp_seq=1 ttl=254 time=34.348 ms
^C
$ doas ntpd -d -s
/var/db/ntpd.drift is empty
ntp engine ready
constraint request to 74.125.130.103
constraint request to 74.125.130.99
constraint request to 74.125.130.147
constraint request to 74.125.130.105
constraint request to 74.125.130.106
constraint request to 74.125.130.104
constraint reply from 74.125.130.147: offset 107.627988
constraint reply from 74.125.130.104: offset 107.625112
constraint reply from 74.125.130.99: offset 107.617672
constraint reply from 74.125.130.105: offset 107.616788
constraint reply from 74.125.130.103: offset 107.613464
constraint reply from 74.125.130.106: offset 107.609782
no reply received in time, skipping initial time setting
no reply from 203.159.70.33 received in time, next query 300s
no reply from 203.158.118.2 received in time, next query 300s
no reply from 203.158.247.150 received in time, next query 300s
no reply from 124.109.2.169 received in time, next query 300s
