[ntp:questions] Re: ntpd as broadcast client not working

Steve Kostecke kostecke at ntp.isc.org
Mon Oct 25 14:33:25 UTC 2004


On 2004-10-25, Tina <tinac at intellambda.com> wrote:

> Here is my server's configure file:
>
> restrict default ignore 
> restrict 127.0.0.1
> server  207.126.98.204
> restrict 207.126.98.204 nomodify

The one thing that you're missing here is a restrict statement to allow
your client subnet to access this broadcast server.

> server  127.127.1.0     # local clock
> fudge   127.127.1.0 stratum 10
> driftfile /etc/ntp/drift
> broadcastdelay  0.008
> authenticate yes
> keys            /etc/ntp/keys
> broadcast 192.168.0.255 key 2 ttl 8

The broadcast line is what tells this particular ntpd to operate as a
broadcast server. You don't need the following broadcastclient line
(unless this server is also the broadcastclient of another broadcast
server.)

> broadcastclient
> trustedkey 2

> And the ntp broadcast client machine has the following in its ntp.conf
> file:
>
> enable auth
> broadcastclient
> #restrict 192.168.0.190 nomodify
> broadcastdelay 0.00800
> driftfile /etc/ntp/drift
> keys      /etc/ntp/keys
> trustedkey 2

-- 
Steve Kostecke <kostecke at ntp.isc.org>



More information about the questions mailing list