Date: Tue, 23 Nov 2004 16:25:29 -0800 From: Evren Yurtesen <yurtesen@ispro.net.tr> To: Yann Golanski <yann@kierun.org>, freebsd-stable@freebsd.org Subject: Re: ntpd v4.2 problem Message-ID: <41A3D4F9.7090001@ispro.net.tr> In-Reply-To: <20041123141250.GB51987@kierun.org> References: <41A3D0F5.1020406@ispro.net.tr> <20041123141250.GB51987@kierun.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yann Golanski wrote: > Quoth Evren Yurtesen on Tue, Nov 23, 2004 at 16:08:21 -0800 > >>The handbook seem to give wrong information about ntp and the manual >>page of ntp.conf is ?old? maybe? >> >>The notrust option obviously changed between v4.1 and v4.2... >>http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ntp.html >> >>Can an ntpd guru have a look into that? > > > My set up is as follows and it works fine on 4.10 and 5.3... > > # cat /etc/ntp.conf > driftfile /var/db/ntp.drift > > server 0.pool.ntp.org > server 1.pool.ntp.org > server 2.pool.ntp.org > > # grep ntp /etc/rc.conf > ntpd_enable="YES" > ntpdate_flags="-b 0.pool.ntp.org" > > But make sure your clocks are in sink at the start by using date. > The problem in the manual is different. You do not have any access control in your server, your server is worldwide open to other people changing your runtime configuration etc. (as it seems from your conf file) From ntp handbook page! ---- If you only want to allow machines within your own network to synchronize their clocks with your server, but ensure they are not allowed to configure the server or used as peers to synchronize against, add restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap ---- But if you use notrust in this line no clients are able to connect. I am not sure why. That is why I asked about an ntpd pro having a look. Thanks, Evren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41A3D4F9.7090001>