Date: Sat, 19 Dec 2009 18:28:10 +0200 From: Omer Faruk Sen <omerfsen@gmail.com> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: ntpq command output and unreachable state? Message-ID: <75a268720912190828k5683aafch28b2c75d35a9d6d0@mail.gmail.com> In-Reply-To: <75a268720912190410x5bd2790du44299c0bbb2aca40@mail.gmail.com> References: <75a268720912190410x5bd2790du44299c0bbb2aca40@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have used ntpq -c associations to see if the server is reachable or not. But even the peers are not reachable my ntpd answers to queries for some time and after recovering connection (reachable state) my ntpd doesn't answer to ntp clients even if ntpq -c peers states "*" state. But after certain amount of time time can be synced with my ntpd server. (this recovery process took more than 1 hour in my test setup). On Sat, Dec 19, 2009 at 2:10 PM, Omer Faruk Sen <omerfsen@gmail.com> wrote: > Hi, > > I am trying to understand output of ntpq -c peers (or ntpq -p). What I > am trying to understand that when a ntp server is announced as > unreachable. I have made a test. I setup a test ntp server with > > > /etc/ntp.conf > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > restrict default nomodify notrap noquery > restrict 127.0.0.1 > server 0.pool.ntp.org > server clock.isc.org > > and started ntpd daemon using > > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f > /var/db/ntpd.drift -g -l /var/log/ntpd.log > > and blocked all port 123 traffic that goes out from this ntp server at > my gateway (to simulate to lost connection on ntp servers at ntp.conf) > After 26 hours later my ntpd still thinks that it can reach to > "clock.isc.org" (as can be seen with "*" mark before clock.isc.org > below) > > # ntpq -c peers > =A0 =A0 remote =A0 =A0 =A0 =A0 =A0 refid =A0 =A0 =A0st t when poll reach = =A0 delay =A0 offset =A0jitter > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > +194.27.110.130 =A0131.188.3.220 =A0 =A02 u =A027h 1024 =A0 =A00 =A0 67.8= 16 =A0 13.282 =A0 0.000 > *clock.isc.org =A0 204.123.2.5 =A0 =A0 =A02 u =A026h 1024 =A0 =A00 =A0224= .461 =A0-15.208 =A0 0.000 > > But I am sure that it can't reach (I sniff my firewall so no traffic > comes from clock.isc.org). My question is how can I find out that my > ntp servers defined at ntp.conf are unreachable (I know that if ntp > server is unreachable than my local ntp server stops to answer for ntp > =A0requests) > > Best Regards. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?75a268720912190828k5683aafch28b2c75d35a9d6d0>