[ntp:questions] NTP Time Server for LAN: Broadcasting or Not?

[ntp:questions] NTP Time Server for LAN: Broadcasting or Not?

Post by Brad Knowl » Tue, 05 Oct 2004 17:52:00

These are all Stratum 1 time servers, some of which are
"restricted access", and at least one of which doesn't seem to be
advertised as a publicly accessible Stratum 1 time server on the
official list at
< http://www.yqcomputer.com/ ;.

You need to re-read the "Rules of Engagement" page at
< http://www.yqcomputer.com/ ; and make sure
you comply with all the restrictions and requirements thereon.

While you're at it, you should also read the community supported
documentation at < http://www.yqcomputer.com/ ;,
especially the page at
< http://www.yqcomputer.com/ ;.

This appears to be a local Stratum 1 time server that you have
set up on a nearby network (it uses RFC 1918 private networking
space), but which appears to be non-functional. You might want to
look into getting this fixed.

You check your clients that are supposed to be receiving those
broadcasts, and see if they are.

Read the official documentation page at
< http://www.yqcomputer.com/ ~mills/ntp/html/ntpq.html>, and pay close
attention to the "Tally Codes" section.

Brad Knowles, < XXXX@XXXXX.COM >

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755

SAGE member since 1995. See < http://www.yqcomputer.com/ ; for more info.

[ntp:questions] NTP Time Server for LAN: Broadcasting or Not?

Post by Steve Kost » Tue, 05 Oct 2004 20:17:25

That line of ntpq output will be visible see on your broadcast server;
it shows the broadcast address for the sub-net you're broadcasting to.
The stratum displays as 16 because that ntpd can't sync to its self. You
would see a similar line on any ntpd which is configured to use its self
as a server.

Steve Kostecke < XXXX@XXXXX.COM >


[ntp:questions] NTP Time Server for LAN: Broadcasting or Not?

Post by maye » Wed, 06 Oct 2004 11:50:54

Right. we really should be dropping this packet as it makes no sense.
I don't think there is a socket option to no receive it's own
broadcast packets. You can turn it off in multicast but the code currently
doesn't do that. It does have the side effect of showing you that you
are running a broadcast server.


[ntp:questions] NTP Time Server for LAN: Broadcasting or Not?

Post by W. D » Wed, 06 Oct 2004 15:01:59

That's kinda what I thought it was saying. The IP address and label:
( .BCST.) were a giveaway. To me, that's helpful info
even if the rest of it is meaningless.

Start Here to Find It Fast!>> http://www.yqcomputer.com/
$8.77 Domain Names >> http://www.yqcomputer.com/

[ntp:questions] NTP Time Server for LAN: Broadcasting or Not?

Post by Danny Maye » Thu, 07 Oct 2004 09:54:28

The real problem here is that the refid is not preventing looping as it should.
Loop prevention should have caused it to drop the packet.