Re: ntpd confusion
Am 24.11.2014 um 06:13 schrieb Chen Wei:
> On Sat, Nov 22, 2014 at 09:57:50PM +0100, mad wrote:
>> # ntpq -p
>> remote refid st t when poll reach delay offset jitter
>> ========================================================================
>> fritz.box X.Y.Z.A 3 u - 64 1 1.874 0.153 0.052
>>
>> I use the default ntp configuration and other Debian installations
>> "directly on the internet" use all four clock sources
>> (0.debian.pool...., 1.debian.pool...).
>>
>
> Why not
>
> 1) double check /etc/ntp.conf, make sure lines such as
> server 0.debian.pool.ntp.org exist.
Already done that multiple times.
> 2) verify remote ntp server is reachable,
> # nmap -sU -p123 0.debian.pool.ntp.org
# nmap -sU -p123 0.debian.pool.ntp.org
Host is up (0.027s latency).
Other addresses for 0.debian.pool.ntp.org (not scanned): 85.10.246.226
141.30.228.4 192.53.103.108
rDNS record for 37.120.166.3: olymp.auf-feindgebiet.de
PORT STATE SERVICE
123/udp open ntp
Nmap done: 1 IP address (1 host up) scanned in 1.70 seconds
> On my system, even the unreachable server shows in "ntpq -p" output.
That is my problem! Not on my internal home network systems. As
mentioned, other Debian installations not on my home network, with the
same configuration show as expected four clock sources. Even starting
ntpd on the command line doesn't show any more data and ntpd is compiled
without debugging. Probably that is what I will do, recompile ntpd with
debug enabled and then see what ntpd is actually doing.
Could it have something to do with upnp, zeroconf or something like that?
mad
Reply to: