über Armbian 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.18-sunxi
habe ich einen NTPServer laufen. Er funktioniert bei den Endgeräten allerdings nur beim zweiten mal.
Das heißt bei der ersten Clientanfrage gibt es keine Uhrzeit zurück und erst bei der zweiten klappt es dann. Und das ist bei jedem Endgerät so sei es ein Windows PC oder eine IP Webcam. Beim erzwungenen dritten, vierten, fünften mal innerhalb kurzer Zeit keine Probleme jedoch mehre Stunden wieder das selbe.
Code: Alles auswählen
root@piserver:~# systemctl status ntp
● ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp; generated; vendor preset: enabled)
Active: active (running) since Sat 2018-03-10 14:38:19 CET; 4s ago
Docs: man:systemd-sysv-generator(8)
Process: 15602 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS)
Process: 15612 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/ntp.service
└─15623 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:110
Mar 10 14:38:19 piserver ntp[15612]: Starting NTP server: ntpd.
Mar 10 14:38:19 piserver systemd[1]: Started LSB: Start NTP daemon.
Mar 10 14:38:19 piserver ntpd[15623]: proto: precision = 1.583 usec (-19)
Mar 10 14:38:19 piserver ntpd[15623]: Listen and drop on 0 v6wildcard [::]:123
Mar 10 14:38:19 piserver ntpd[15623]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Mar 10 14:38:19 piserver ntpd[15623]: Listen normally on 2 lo 127.0.0.1:123
Mar 10 14:38:19 piserver ntpd[15623]: Listen normally on 3 eth0 192.168.1.21:123
Mar 10 14:38:19 piserver ntpd[15623]: Listen normally on 4 lo [::1]:123
Mar 10 14:38:19 piserver ntpd[15623]: Listen normally on 5 eth0 [fe80::44:8ff:fe09:84fd%2]:123
Mar 10 14:38:19 piserver ntpd[15623]: Listening on routing socket on fd #22 for interface updates
Code: Alles auswählen
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
driftfile /var/lib/ntp/ntp.drift
# Enable this if you want statistics to be logged.
#statsdir /var/log/ntpstats/
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example
# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
# pick a different set every time it starts up. Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
server 1.de.pool.ntp.org
server 2.de.pool.ntp.org
server ntp1.hetzner.de iburst
server ntp2.hetzner.com iburst
server ntp3.hetzner.net iburst
# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.
# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited
# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1
restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
# Needed for adding pool entries
restrict source notrap nomodify noquery
# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust
# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
broadcast 192.168.1.255
# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines. Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient
Code: Alles auswählen
ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
195.50.171.101 145.253.2.212 2 u 6 64 1 54.116 9.693 0.002
panel1.web2.clu 5.189.146.13 3 u 6 64 1 56.251 11.769 0.002
*ntp1.hetzner.de 192.53.103.103 2 u - 64 1 63.190 0.718 0.207
+ntp2.hetzner.de 124.216.164.14 2 u 1 64 1 67.328 2.192 0.137
+ntp3.hetzner.de 192.53.103.108 2 u 1 64 1 66.064 0.636 0.048
Da sind keine Firewalldienste akitv und DNSMasq auch abgeschaltet.