Reply To: Ntpd don’t synchronize with remote time servers

Home Page Forums Network Management ZeroShell Ntpd don’t synchronize with remote time servers Reply To: Ntpd don’t synchronize with remote time servers

#51215

turboon
Member

NTP Configuration:

Ping:

root@zeroshell root> ping ntp0.fau.de
PING ntp0.rrze.uni-erlangen.de (131.188.3.220) 56(84) bytes of data.
64 bytes from ntp0.rrze.uni-erlangen.de (131.188.3.220): icmp_seq=1 ttl=53 time=102 ms
64 bytes from ntp0.rrze.uni-erlangen.de (131.188.3.220): icmp_seq=2 ttl=53 time=102 ms
64 bytes from ntp0.rrze.uni-erlangen.de (131.188.3.220): icmp_seq=3 ttl=53 time=101 ms
64 bytes from ntp0.rrze.uni-erlangen.de (131.188.3.220): icmp_seq=4 ttl=53 time=101 ms
^C
— ntp0.rrze.uni-erlangen.de ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3015ms
rtt min/avg/max/mdev = 101.649/102.202/102.895/0.603 ms

root@zeroshell root> ping 1.pool.ntp.org
PING 1.pool.ntp.org (85.21.78.91) 56(84) bytes of data.
64 bytes from ground.corbina.net (85.21.78.91): icmp_seq=1 ttl=57 time=21.5 ms
64 bytes from ground.corbina.net (85.21.78.91): icmp_seq=2 ttl=57 time=21.2 ms
64 bytes from ground.corbina.net (85.21.78.91): icmp_seq=3 ttl=57 time=21.5 ms
64 bytes from ground.corbina.net (85.21.78.91): icmp_seq=4 ttl=57 time=20.6 ms
^C
— 1.pool.ntp.org ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3013ms
rtt min/avg/max/mdev = 20.649/21.242/21.589/0.408 ms

root@zeroshell root> ping 2.pool.ntp.org
PING 2.pool.ntp.org (77.105.134.138) 56(84) bytes of data.
64 bytes from h77-105-134-138.plustelecom.ru (77.105.134.138): icmp_seq=1 ttl=58 time=37.9 ms
64 bytes from h77-105-134-138.plustelecom.ru (77.105.134.138): icmp_seq=2 ttl=58 time=37.6 ms
64 bytes from h77-105-134-138.plustelecom.ru (77.105.134.138): icmp_seq=3 ttl=58 time=37.5 ms
64 bytes from h77-105-134-138.plustelecom.ru (77.105.134.138): icmp_seq=4 ttl=58 time=37.7 ms
^C
— 2.pool.ntp.org ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3012ms
rtt min/avg/max/mdev = 37.536/37.716/37.903/0.131 ms

iptables -L -v is too long to post it here 🙂
but I turn
iptables -P INPUT ACCEPT
and
iptables -P OUTPUT ACCEPT for experimental reasons at this time

For addition – ntpdate results:

root@zeroshell root> ntpdate -q ntp0.fau.de
server 131.188.3.220, stratum 1, offset -928.084942, delay 0.11633
19 Oct 10:49:23 ntpdate[13580]: step time server 131.188.3.220 offset -928.08494 2 sec

root@zeroshell root> ntpdate -q 0.pool.ntp.org
server 85.21.78.23, stratum 2, offset -928.267751, delay 0.04602
server 195.16.46.183, stratum 2, offset -928.272155, delay 0.04547
server 212.1.243.55, stratum 3, offset -928.272996, delay 0.04478
19 Oct 10:49:37 ntpdate[13686]: step time server 195.16.46.183 offset -928.27215 5 sec

root@zeroshell root> ntpdate -q 1.pool.ntp.org
server 91.194.10.40, stratum 2, offset -928.321728, delay 0.04489
server 212.192.253.168, stratum 3, offset -928.336857, delay 0.05846
server 77.234.200.98, stratum 3, offset -928.331364, delay 0.05228
19 Oct 10:49:41 ntpdate[13746]: step time server 91.194.10.40 offset -928.321728 sec

root@zeroshell root> ntpdate -q 2.pool.ntp.org
server 195.144.29.10, stratum 3, offset -928.366761, delay 0.02785
server 83.229.210.18, stratum 3, offset -928.373302, delay 0.06274
server 193.169.32.220, stratum 3, offset -928.373573, delay 0.04349
19 Oct 10:49:44 ntpdate[13751]: step time server 195.144.29.10 offset -928.36676 1 sec