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. > >>>>> Root Dispersion: 3,9689 sec > ... >>> So optimally that should be 0? >>> Is there a limit defined in the ntp spec? >> MAXDIST. 1 second in the reference implementation, which >> is a bit generous. > > like bigger than the 1 second in the ref.impl.? the spec and the reference implementation agree. Which is sorta the whole point of a reference implementation, IMHO. > > > Folkert van Heusden > > -- > Looking for a cheap but fast webhoster with an excellent helpdesk? > http://keetweej.vanheusden.com/redir.php?id=1001 > ---------------------------------------------------------------------- > Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com > _______________________________________________ > questions mailing list > questions@lists.ntp.org > https://lists.ntp.org/mailman/listinfo/questions > _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
