Jim MacKenzie wrote:
Did you try to do an NTP query while you had tcpdump running?
The output can help us determine if your traffic is getting out, and if
anything is coming back.
That's a good one. I did try one from outside, but that obviously didn't work. I
started another Ubuntu computer and got more output, not just from my workings.
No idea where this comes from, but I still can't get at it from outside. The
output is attached to the mail.
ubilap.lan.ntp is my server, ubuntu.lan.ntp is the computer I tested from (both
ntpq -p and ntpdate work).
There is also an polkadot.maasluip.nl.ntp, that's my windows computer.
I've also included my ntp.conf file.
Maarten
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Maarten Deen
Sent: January 16, 2009 3:52 PM
To: timekeepers
Subject: Re: [time] Trouble configuring ntp
This is the output of approx. 15 minutes:
maar...@ubilap:~$ sudo tcpdump -i eth0 port 123
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
22:38:21.510268 IP ubilap.lan.ntp > 195-241-158-50.ip.telfort.nl.ntp: NTPv4,
Client, length 48
22:38:21.543414 IP 195-241-158-50.ip.telfort.nl.ntp > ubilap.lan.ntp: NTPv3,
Server, length 48
2 packets captured
2 packets received by filter
0 packets dropped by kernel
Not very impressive I think.
Maarten
Jim MacKenzie wrote:
What happens if you do a tcpdump sniff on your Ubuntu box?
tcpdump -i eth0 (or eth1 or whatever) port 123
You might have to sudo it on Ubuntu.
Jim
----- Original Message -----
From: "Maarten Deen" <[email protected]>
To: "timekeepers" <[email protected]>
Sent: Thursday, January 15, 2009 4:25 PM
Subject: [time] Trouble configuring ntp
I just had my server crash and I'm now having trouble getting ntp to run
properly again.
It is Ubuntu 8.04 with normal ntp.
On my machine everything seems to work. I can query ntp on the machine
itself
and I get a time when I ask from a windows computer.
But it does not seem to be accessible remotely.
I've tried removing all restrict lines from ntp.conf (I did restart ntp),
but
that does not seem to work. My firewall is configured to allow UDP port
123
pass. Yet, an ntpq -p results in a timeout.
http://www.vanheusden.com/time/query_ntp_do.php tells me:
Query NTP server
If 82.95.91.106 is part of the NTP pool project, one can check its
performance here.
Output of NTP server at 82.95.91.106
ntpdate
15 Jan 23:16:23 ntpdate[7063]: ntpdate [email protected] Tue Sep 23 17:37:40
UTC
2003 (1)
server 82.95.91.106, stratum 0, offset 0.000000, delay 0.00000
ntpq -c pe
ntpq -crv
ntpq -c ntpversion -c version
NTP version being claimed is 2
ntpq [email protected] Tue Sep 23 17:38:05 UTC 2003 (1)
ntpq -c associations
ntptrace
maasluip.xs4all.nl: *Timeout*
I'm at a loss here. Can anyone help?
Maarten
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
maar...@ubilap:~$ sudo tcpdump -i eth0 port 123
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
22:50:55.985520 IP 169.254.2.2.ntp > 7of9.lastdot.org.ntp: NTPv3, symmetric
active, length 48
22:50:55.985595 IP polkadot.maasluip.nl.ntp > 7of9.lastdot.org.ntp: NTPv3,
symmetric active, length 48
22:50:55.985682 IP 169.254.2.2.ntp > ntp2.hro.nl.ntp: NTPv3, symmetric active,
length 48
22:50:55.985776 IP polkadot.maasluip.nl.ntp > ntp2.hro.nl.ntp: NTPv3, symmetric
active, length 48
22:50:55.985865 IP 169.254.2.2.ntp > nfs01.ip2.net.ntp: NTPv3, symmetric
active, length 48
22:50:55.985957 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:50:55.986047 IP 169.254.2.2.ntp > metronoom.dmz.cs.uu.nl.ntp: NTPv3,
symmetric active, length 48
22:50:55.986138 IP polkadot.maasluip.nl.ntp > metronoom.dmz.cs.uu.nl.ntp:
NTPv3, symmetric active, length 48
22:50:55.986231 IP 169.254.2.2.ntp > edge.tillo.ch.ntp: NTPv3, symmetric
active, length 48
22:50:55.986319 IP polkadot.maasluip.nl.ntp > edge.tillo.ch.ntp: NTPv3,
symmetric active, length 48
22:50:55.986415 IP 169.254.2.2.ntp > hosted-by.leaseweb.com.ntp: NTPv3,
symmetric active, length 48
22:50:55.986501 IP polkadot.maasluip.nl.ntp > hosted-by.leaseweb.com.ntp:
NTPv3, symmetric active, length 48
22:50:55.986595 IP 169.254.2.2.ntp > ntp.ses-newskies.com.ntp: NTPv3, symmetric
active, length 48
22:50:55.986685 IP polkadot.maasluip.nl.ntp > ntp.ses-newskies.com.ntp: NTPv3,
symmetric active, length 48
22:50:55.986776 IP 169.254.2.2.ntp > server.jorijn.com.ntp: NTPv3, symmetric
active, length 48
22:50:55.986869 IP polkadot.maasluip.nl.ntp > server.jorijn.com.ntp: NTPv3,
symmetric active, length 48
22:50:55.986983 IP 169.254.2.2.ntp > ntp1.hro.nl.ntp: NTPv3, symmetric active,
length 48
22:50:55.987051 IP polkadot.maasluip.nl.ntp > ntp1.hro.nl.ntp: NTPv3, symmetric
active, length 48
22:50:55.987142 IP 169.254.2.2.ntp > minian.org.ntp: NTPv3, symmetric active,
length 48
22:50:55.987233 IP polkadot.maasluip.nl.ntp > minian.org.ntp: NTPv3, symmetric
active, length 48
22:50:55.987327 IP 169.254.2.2.ntp > sectionzero.org.ntp: NTPv3, symmetric
active, length 48
22:50:55.987412 IP polkadot.maasluip.nl.ntp > sectionzero.org.ntp: NTPv3,
symmetric active, length 48
22:50:55.987508 IP 169.254.2.2.ntp > colo.farenji.net.ntp: NTPv3, symmetric
active, length 48
22:50:55.987597 IP polkadot.maasluip.nl.ntp > colo.farenji.net.ntp: NTPv3,
symmetric active, length 48
22:50:55.987690 IP 169.254.2.2.ntp > 213.206.97.167.ntp: NTPv3, symmetric
active, length 48
22:50:55.987780 IP polkadot.maasluip.nl.ntp > 213.206.97.167.ntp: NTPv3,
symmetric active, length 48
22:50:55.987871 IP 169.254.2.2.ntp > ns2.mainloop.net.ntp: NTPv3, symmetric
active, length 48
22:50:55.988003 IP polkadot.maasluip.nl.ntp > ns2.mainloop.net.ntp: NTPv3,
symmetric active, length 48
22:50:55.988057 IP 169.254.2.2.ntp > muso.komputilo.org.ntp: NTPv3, symmetric
active, length 48
22:50:55.988144 IP polkadot.maasluip.nl.ntp > muso.komputilo.org.ntp: NTPv3,
symmetric active, length 48
22:50:55.997261 IP 7of9.lastdot.org.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric active, length 48
22:50:56.002687 IP metronoom.dmz.cs.uu.nl.ntp > polkadot.maasluip.nl.ntp:
NTPv3, symmetric active, length 48
22:50:56.003143 IP ntp2.hro.nl.ntp > polkadot.maasluip.nl.ntp: NTPv3, symmetric
active, length 48
22:50:56.004150 IP edge.tillo.ch.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric active, length 48
22:50:56.005419 IP hosted-by.leaseweb.com.ntp > polkadot.maasluip.nl.ntp:
NTPv3, symmetric active, length 48
22:50:56.009623 IP server.jorijn.com.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric active, length 48
22:50:56.011568 IP ntp.ses-newskies.com.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric passive, length 48
22:50:56.012299 IP minian.org.ntp > polkadot.maasluip.nl.ntp: NTPv3, symmetric
active, length 48
22:50:56.014568 IP sectionzero.org.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric passive, length 48
22:50:56.015249 IP ntp1.hro.nl.ntp > polkadot.maasluip.nl.ntp: NTPv3, symmetric
active, length 48
22:50:56.017489 IP colo.farenji.net.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric active, length 48
22:50:56.017729 IP 213.206.97.167.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric active, length 48
22:50:56.019929 IP ns2.mainloop.net.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric active, length 48
22:50:56.020675 IP muso.komputilo.org.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric active, length 48
22:51:44.710404 IP srv01.ip2.net.ntp > polkadot.maasluip.nl.ntp: NTPv3,
symmetric passive, length 48
22:52:00.000675 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:53:04.000197 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:54:06.510314 IP ubilap.lan.ntp > auth1.xs4all.nl.ntp: NTPv4, Client, length
48
22:54:06.525859 IP auth1.xs4all.nl.ntp > ubilap.lan.ntp: NTPv4, Server, length
48
22:54:07.999709 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:54:15.510281 IP ubilap.lan.ntp > ntp2.belbone.be.ntp: NTPv4, Client, length
48
22:54:15.528254 IP ntp2.belbone.be.ntp > ubilap.lan.ntp: NTPv4, Server, length
48
22:55:11.999227 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:55:21.510307 IP ubilap.lan.ntp > ns2.madavi.de.ntp: NTPv4, Client, length 48
22:55:21.542434 IP ns2.madavi.de.ntp > ubilap.lan.ntp: NTPv4, Server, length 48
22:55:25.510305 IP ubilap.lan.ntp > 195-241-158-50.ip.telfort.nl.ntp: NTPv4,
Client, length 48
22:55:25.544643 IP 195-241-158-50.ip.telfort.nl.ntp > ubilap.lan.ntp: NTPv3,
Server, length 48
22:56:15.998760 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:56:47.999362 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:57:03.998457 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:57:19.998277 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:57:35.998165 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:57:51.998138 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:58:07.997951 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:58:11.823496 IP ubuntu.lan.ntp > europium.canonical.com.ntp: NTPv4, Client,
length 48
22:58:11.841899 IP europium.canonical.com.ntp > ubuntu.lan.ntp: NTPv4, Server,
length 48
22:58:11.842273 IP ubuntu.lan.ntp > europium.canonical.com.ntp: NTPv4, Client,
length 48
22:58:11.860363 IP europium.canonical.com.ntp > ubuntu.lan.ntp: NTPv4, Server,
length 48
22:58:11.863476 IP ubuntu.lan.ntp > europium.canonical.com.ntp: NTPv4, Client,
length 48
22:58:11.881078 IP europium.canonical.com.ntp > ubuntu.lan.ntp: NTPv4, Server,
length 48
22:58:11.881348 IP ubuntu.lan.ntp > europium.canonical.com.ntp: NTPv4, Client,
length 48
22:58:11.899559 IP europium.canonical.com.ntp > ubuntu.lan.ntp: NTPv4, Server,
length 48
22:58:23.997841 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:58:39.997805 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:58:55.997613 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:59:12.013233 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:59:26.700540 IP 169.254.2.2.ntp > 7of9.lastdot.org.ntp: NTPv3, symmetric
active, length 48
22:59:26.700615 IP 169.254.2.2.ntp > ntp2.hro.nl.ntp: NTPv3, symmetric active,
length 48
22:59:26.700705 IP 169.254.2.2.ntp > nfs01.ip2.net.ntp: NTPv3, symmetric
active, length 48
22:59:26.700797 IP 169.254.2.2.ntp > metronoom.dmz.cs.uu.nl.ntp: NTPv3,
symmetric active, length 48
22:59:26.700888 IP 169.254.2.2.ntp > edge.tillo.ch.ntp: NTPv3, symmetric
active, length 48
22:59:26.700979 IP 169.254.2.2.ntp > hosted-by.leaseweb.com.ntp: NTPv3,
symmetric active, length 48
22:59:26.701070 IP 169.254.2.2.ntp > ntp.ses-newskies.com.ntp: NTPv3, symmetric
active, length 48
22:59:26.701162 IP 169.254.2.2.ntp > server.jorijn.com.ntp: NTPv3, symmetric
active, length 48
22:59:26.701252 IP 169.254.2.2.ntp > ntp1.hro.nl.ntp: NTPv3, symmetric active,
length 48
22:59:26.701344 IP 169.254.2.2.ntp > minian.org.ntp: NTPv3, symmetric active,
length 48
22:59:26.701434 IP 169.254.2.2.ntp > sectionzero.org.ntp: NTPv3, symmetric
active, length 48
22:59:26.701526 IP 169.254.2.2.ntp > colo.farenji.net.ntp: NTPv3, symmetric
active, length 48
22:59:26.701619 IP 169.254.2.2.ntp > 213.206.97.167.ntp: NTPv3, symmetric
active, length 48
22:59:26.701726 IP 169.254.2.2.ntp > ns2.mainloop.net.ntp: NTPv3, symmetric
active, length 48
22:59:26.701798 IP 169.254.2.2.ntp > muso.komputilo.org.ntp: NTPv3, symmetric
active, length 48
22:59:27.981777 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:59:43.981698 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
22:59:59.981558 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:00:15.981441 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:00:31.981302 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:00:47.981202 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:01:03.981102 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:01:19.981002 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:01:35.980902 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:01:51.980787 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:02:07.980673 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:02:23.980580 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:02:39.980528 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:02:42.266174 IP ubuntu.lan.ntp > europium.canonical.com.ntp: NTPv4, Client,
length 48
23:02:42.284252 IP europium.canonical.com.ntp > ubuntu.lan.ntp: NTPv4, Server,
length 48
23:02:46.178352 IP ubuntu.lan.33957 > ubilap.lan.ntp: NTPv2, Reserved, length 12
23:02:46.210916 IP ubilap.lan.ntp > ubuntu.lan.33957: NTPv2, Reserved, length 28
23:02:46.222889 IP ubuntu.lan.33957 > ubilap.lan.ntp: NTPv2, Reserved, length 12
23:02:46.224091 IP ubilap.lan.ntp > ubuntu.lan.33957: NTPv2, Reserved, length
440
23:02:46.224308 IP ubilap.lan.ntp > ubuntu.lan.33957: NTPv2, Reserved, length
184
23:02:46.250924 IP ubuntu.lan.33957 > ubilap.lan.ntp: NTPv2, Reserved, length 12
23:02:46.251858 IP ubilap.lan.ntp > ubuntu.lan.33957: NTPv2, Reserved, length
444
23:02:46.251979 IP ubilap.lan.ntp > ubuntu.lan.33957: NTPv2, Reserved, length
196
23:02:46.270650 IP ubuntu.lan.33957 > ubilap.lan.ntp: NTPv2, Reserved, length 12
23:02:46.271540 IP ubilap.lan.ntp > ubuntu.lan.33957: NTPv2, Reserved, length
440
23:02:46.271666 IP ubilap.lan.ntp > ubuntu.lan.33957: NTPv2, Reserved, length
192
23:02:46.289220 IP ubuntu.lan.33957 > ubilap.lan.ntp: NTPv2, Reserved, length 12
23:02:46.289893 IP ubilap.lan.ntp > ubuntu.lan.33957: NTPv2, Reserved, length
440
23:02:46.289985 IP ubilap.lan.ntp > ubuntu.lan.33957: NTPv2, Reserved, length
196
23:02:55.980367 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:03:11.980269 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:03:27.980166 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
23:03:32.705864 IP ubuntu.lan.ntp > ubilap.lan.ntp: NTPv4, Client, length 48
23:03:32.706208 IP ubilap.lan.ntp > ubuntu.lan.ntp: NTPv4, Server, length 48
23:03:32.706573 IP ubuntu.lan.ntp > ubilap.lan.ntp: NTPv4, Client, length 48
23:03:32.706682 IP ubilap.lan.ntp > ubuntu.lan.ntp: NTPv4, Server, length 48
23:03:32.706996 IP ubuntu.lan.ntp > ubilap.lan.ntp: NTPv4, Client, length 48
23:03:32.707108 IP ubilap.lan.ntp > ubuntu.lan.ntp: NTPv4, Server, length 48
23:03:32.707415 IP ubuntu.lan.ntp > ubilap.lan.ntp: NTPv4, Client, length 48
23:03:32.707524 IP ubilap.lan.ntp > ubuntu.lan.ntp: NTPv4, Server, length 48
23:03:42.089424 IP 169.254.2.2.ntp > 7of9.lastdot.org.ntp: NTPv3, symmetric
active, length 48
23:03:42.089498 IP 169.254.2.2.ntp > ntp2.hro.nl.ntp: NTPv3, symmetric active,
length 48
23:03:42.089584 IP 169.254.2.2.ntp > nfs01.ip2.net.ntp: NTPv3, symmetric
active, length 48
23:03:42.089678 IP 169.254.2.2.ntp > metronoom.dmz.cs.uu.nl.ntp: NTPv3,
symmetric active, length 48
23:03:42.089769 IP 169.254.2.2.ntp > edge.tillo.ch.ntp: NTPv3, symmetric
active, length 48
23:03:42.089858 IP 169.254.2.2.ntp > hosted-by.leaseweb.com.ntp: NTPv3,
symmetric active, length 48
23:03:42.089952 IP 169.254.2.2.ntp > ntp.ses-newskies.com.ntp: NTPv3, symmetric
active, length 48
23:03:42.090041 IP 169.254.2.2.ntp > server.jorijn.com.ntp: NTPv3, symmetric
active, length 48
23:03:42.090133 IP 169.254.2.2.ntp > ntp1.hro.nl.ntp: NTPv3, symmetric active,
length 48
23:03:42.090223 IP 169.254.2.2.ntp > minian.org.ntp: NTPv3, symmetric active,
length 48
23:03:42.090314 IP 169.254.2.2.ntp > sectionzero.org.ntp: NTPv3, symmetric
active, length 48
23:03:42.090406 IP 169.254.2.2.ntp > colo.farenji.net.ntp: NTPv3, symmetric
active, length 48
23:03:42.090511 IP 169.254.2.2.ntp > 213.206.97.167.ntp: NTPv3, symmetric
active, length 48
23:03:42.090587 IP 169.254.2.2.ntp > ns2.mainloop.net.ntp: NTPv3, symmetric
active, length 48
23:03:42.090680 IP 169.254.2.2.ntp > muso.komputilo.org.ntp: NTPv3, symmetric
active, length 48
23:03:43.948782 IP polkadot.maasluip.nl.ntp > nfs01.ip2.net.ntp: NTPv3,
symmetric active, length 48
147 packets captured
147 packets received by filter
0 packets dropped by kernel
# /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.xs4all.nl
server serv01.richs.nl
server ntp3.madavi.de
server ntp2.belbone.be
# 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
#restrict -6 default kod notrap nomodify nopeer noquery
# Local users may interrogate the ntp server more closely.
#restrict 127.0.0.1
#restrict ::1
# 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.123.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
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
