- Joined
- May 19, 2017
- Messages
- 1,829
Wonder if your ISP is limiting access or your IP address/block was flagged for excess NTP requests?
my ISP (EDPnet in Belgium) was blocking port 123 in such a way that NTP client traffic didn't work
data# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== ntp.cybertu.be .INIT. 16 u - 1024 0 0.000 +0.000 0.000 ntp2.unix-solut .INIT. 16 u - 1024 0 0.000 +0.000 0.000 dns-rec-2-brudi .INIT. 16 u - 1024 0 0.000 +0.000 0.000 data# service ntpd stop Stopping ntpd. Waiting for PIDS: 59836. data# ntpdate -v pool.ntp.org 6 Dec 15:05:09 ntpdate[59268]: ntpdate 4.2.8p15-a (1) 6 Dec 15:05:18 ntpdate[59268]: no server suitable for synchronization found
data# ntpdate -q -u -v -d -4 pool.ntp.org 6 Dec 15:12:09 ntpdate[59400]: ntpdate 4.2.8p15-a (1) transmit(162.159.200.1) receive(162.159.200.1) transmit(91.121.216.238) receive(91.121.216.238) transmit(78.129.36.63) receive(78.129.36.63) transmit(45.87.78.35) receive(45.87.78.35) server 162.159.200.1, port 123 stratum 3, precision -25, leap 00, trust 000 refid [10.78.8.138], root delay 0.006165, root dispersion 0.000351 reference time: e5589866.53f772b0 Mon, Dec 6 2021 15:10:46.327 originate timestamp: e55898de.6ffa5451 Mon, Dec 6 2021 15:12:46.437 transmit timestamp: e55898b9.8695b0ac Mon, Dec 6 2021 15:12:09.525 delay 0.03613, dispersion 0.00000, offset +36.906350 server 91.121.216.238, port 123 stratum 2, precision -24, leap 00, trust 000 refid [193.190.230.37], root delay 0.004517, root dispersion 0.029449 reference time: e55895b2.cdcb4ea7 Mon, Dec 6 2021 14:59:14.803 originate timestamp: e55898de.a50468dd Mon, Dec 6 2021 15:12:46.644 transmit timestamp: e55898b9.bb619eb0 Mon, Dec 6 2021 15:12:09.731 delay 0.03914, dispersion 0.00000, offset +36.905817 server 78.129.36.63, port 123 stratum 3, precision -22, leap 00, trust 000 refid [193.190.198.14], root delay 0.011200, root dispersion 0.115738 reference time: e558981c.af5df9ab Mon, Dec 6 2021 15:09:32.685 originate timestamp: e55898de.d90df016 Mon, Dec 6 2021 15:12:46.847 transmit timestamp: e55898b9.ee94a91e Mon, Dec 6 2021 15:12:09.931 delay 0.04633, dispersion 0.00000, offset +36.905506 server 45.87.78.35, port 123 stratum 2, precision -25, leap 00, trust 000 refid [109.68.160.223], root delay 0.000610, root dispersion 0.001068 reference time: e55895ca.650e9eba Mon, Dec 6 2021 14:59:38.394 originate timestamp: e55898df.08fd426e Mon, Dec 6 2021 15:12:47.035 transmit timestamp: e55898ba.1fa77a5c Mon, Dec 6 2021 15:12:10.123 delay 0.03653, dispersion 0.00000, offset +36.905996 6 Dec 15:12:10 ntpdate[59400]: step time server 45.87.78.35 offset +36.905996 sec
data# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== +ntp.rack66.net 193.79.237.14 2 u 58 64 377 11.066 +7.634 0.301 +94-224-67-24.ac 192.53.103.108 2 u 25 64 377 21.906 +7.806 1.934 *ntp1.unix-solut 85.82.99.131 2 u 18 64 377 10.474 +7.758 0.473 data# service ntpd stop Stopping ntpd. Waiting for PIDS: 59836. data# ntdate -v pool.ntp.org -su: ntdate: command not found data# ntpdate -v pool.ntp.org 6 Dec 21:33:54 ntpdate[65916]: ntpdate 4.2.8p15-a (1) 6 Dec 21:34:01 ntpdate[65916]: adjust time server 45.87.76.3 offset +0.008038 sec
working again (even without the '-u')
Only after my ISP unblocked port 123, it started working again. So I guess that my ISP actually did block '*:123' instead of 'me:123'.