[ntp:questions] ntpdate refusing ntp.nmi.nl
Unruh
unruh-spam at physics.ubc.ca
Sat Jan 10 00:15:42 UTC 2009
hundoj at comcast.net (Rob Neal) writes:
>On Fri, 9 Jan 2009, Folkert van Heusden wrote:
>> Hi,
>>
>> Got one question:
>>
>>>>>>> reference time: cd0c473b.73087696 Mon, Jan 5 2009 9:45:47.449
>>>>>>> ( http://nmi.nl/index.php?pageId=1215&lg=nl )
>>>>>> A wireshark capture shows that it sends a bogu reftime ...
>>>>>> Reference Clock Update Time: Jan 5, 2009 08:45:47,4493 UTC
>>>>
>>>> Does a valid NTP source need to set the reftime to something valid? Does
>>>> the ntp spec say so?
>>> Yes.
>>> Quote 'Time when the system clock was last set or corrected,
>>> in NTP timestamp format' unquote.
>>
>> So this can be years in the past? If so: why is ntpdate then refusing
>> this server? Is it because of the huge root dispersion?
> Yes.
> You don't want to trust this time source. Use a pool server
> and move on. The folk providing this time source either don't
> understand how to operate a server or don't care enough to
> monitor its performance.
Which is a bit weird for a standards organization. It is like if a car
company was found not to know what an engine was or how they operate.
More information about the questions
mailing list