From owner-freebsd-questions@FreeBSD.ORG Sat Dec 19 12:10:42 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDC27106568D for ; Sat, 19 Dec 2009 12:10:42 +0000 (UTC) (envelope-from omerfsen@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 688788FC08 for ; Sat, 19 Dec 2009 12:10:41 +0000 (UTC) Received: by fxm27 with SMTP id 27so3552071fxm.3 for ; Sat, 19 Dec 2009 04:10:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Lygxaa0KhQNy+zofr1jNOjqDXhlvCSOKZCc7tmcthdk=; b=UOaC4wJxEplNBw/MzHshQFSHsYC1PRANYuPrpOTo+SqWHxwKJ13Xs0fazPSGN2PnVB AaG3yJPwyoeNvsQpijsqwGSuDpCCFjIeHhQZ1PZ3PDmgaWnMgoLlaCBlJjWvRhjX3RFj RzEZQoRT1c90IU2o8+QLXkArL1rxZw1FXzZY4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=PjjQPrjBlmNVsw0SKR+s+WnT6Eaw3Z7FElS4lLtp5PJNlyonzSRcXt0+bUsRnyCDnL VA4oTKFH/Lrnx7FWxU8PMIe6gNBMXfB7v3VwzzBdVFZJZasQo3gBI4Uq5YRLDHdU29cE CQrE63tURGqcwUWphghNERDEfoI38thsnP7QM= MIME-Version: 1.0 Received: by 10.239.145.142 with SMTP id s14mr514293hba.144.1261224640291; Sat, 19 Dec 2009 04:10:40 -0800 (PST) Date: Sat, 19 Dec 2009 14:10:40 +0200 Message-ID: <75a268720912190410x5bd2790du44299c0bbb2aca40@mail.gmail.com> From: Omer Faruk Sen To: FreeBSD Content-Type: text/plain; charset=ISO-8859-1 Subject: ntpq command output and unreachable state? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 12:10:42 -0000 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 ============= 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 remote refid st t when poll reach delay offset jitter ============================================================================== +194.27.110.130 131.188.3.220 2 u 27h 1024 0 67.816 13.282 0.000 *clock.isc.org 204.123.2.5 2 u 26h 1024 0 224.461 -15.208 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 requests) Best Regards.