[ntp:questions] Re: refid on client differs from refid on local server

Harlan Stenn stenn at ntp.isc.org
Fri Dec 16 09:29:50 UTC 2005

Path: news.isc.org!newsfeed.stanford.edu!headwall.stanford.edu!newsfeed.news2me.com!newsfeed.icl.net!news-lond.gip.net!news.gsl.net!gip.net!colt.net!news.nl.colt.net!newsgate.cistron.nl!amsnews11.chello.com!border2.nntp.ams.giganews.com!nntp.giganews.com!pe2.news.blueyonder.co.uk!blueyonder!pe1.news.blueyonder.co.uk!blueyonder!text.news.blueyonder.co.uk!53ab2750!not-for-mail
From: "David J Taylor" <david-taylor at blueyonder.co.not-this-bit.nor-this-part.uk.invalid>
Newsgroups: comp.protocols.time.ntp
References: <200512152216.23094.cave.dnb at tiscali.fr> <43A22E11.2030203 at ntp.isc.org>
Subject: Re: refid on client differs from refid on local server
Lines: 20
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-RFC2646: Format=Flowed; Original
Message-ID: <A8vof.9715$iz3.6572 at text.news.blueyonder.co.uk>
Date: Fri, 16 Dec 2005 08:45:20 GMT
X-Complaints-To: abuse at blueyonder.co.uk
X-Trace: text.news.blueyonder.co.uk 1134722720 (Fri, 16 Dec 2005 08:45:20 GMT)
NNTP-Posting-Date: Fri, 16 Dec 2005 08:45:20 GMT
Xref: news.isc.org comp.protocols.time.ntp:39464

Danny Mayer wrote:
>> Sigh. Please repeat after me: A refid is NOT an IP address, it's a
>> 32-bit number that is used for loop prevention.

David wrote:
> It's very helpful to it as an IP address.  Is there no way we could get 
> both?

How?  It's a 32 bit field.  We can have IPv4 or a hashed IPv6 address there,
and I don't believe the client can tell which it is.  And I think it is now
possible to have a refclock that is running at a stratum "worse" than S1.

What is wrong with using ntptrace for this?


More information about the questions mailing list