From owner-freebsd-questions Thu Aug 10 18: 9:39 2000 Delivered-To: freebsd-questions@freebsd.org Received: from thoth.amduat.net (c500290-a.frndl1.wa.home.com [24.10.38.147]) by hub.freebsd.org (Postfix) with ESMTP id 8A22037BBA8 for ; Thu, 10 Aug 2000 18:09:34 -0700 (PDT) (envelope-from jsbarrett@acm.org) Received: from acm.org ([63.89.163.150]) by thoth.amduat.net (8.9.3/8.9.3) with ESMTP id SAA06520 for ; Thu, 10 Aug 2000 18:09:41 -0700 (PDT) (envelope-from jsbarrett@acm.org) Message-ID: <3993529A.7F96AF1C@acm.org> Date: Thu, 10 Aug 2000 18:10:50 -0700 From: "Jacob S. Barrett" Reply-To: jbarrett@amduat.net X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: NTP and FreeBSD 4.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since I have upgraded to FreeBSD 4.1 the NTP ntpd port has stopped synching. It acts like it is but puts all the ntp servers on the reject list. Are there any known issues with ntp-4.0.99i and FreeBSD 4.1. Under 4.0 it worked just fine. It looks to me, but I am not 100% familiar with the correct values, that ntp is factoring the offset times incorrectly for some reason. Here is some debug output to show what I mean. ntpd -D 2: peer 204.123.2.72 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) poll_update: at 19 204.123.2.72 poll 6 burst 0 last 19 next 85 clock_filter: offset -3.185361 delay 0.044835 disp 7.937508 std 2.979632, age 0 receive: from 204.34.198.40 restrict 00 receive: at 19 from 204.34.198.40 mode 4 pkt_mode 4 action 1 peer 204.34.198.40 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) poll_update: at 19 204.34.198.40 poll 6 burst 0 last 19 next 83 clock_filter: offset -3.200164 delay 0.171138 disp 7.937515 std 2.993479, age 0 ntpq: ntpq> pe remote refid st t when poll reach delay offset jitter ============================================================================== bigben.cac.wash .USNO. 1 u 11 64 1 24.123 -3177.3 2972.13 204.34.198.40 .USNO. 1 u 9 64 1 171.138 -3200.1 2993.47 usno.pa-x.dec.c .USNO. 1 u 10 64 1 44.835 -3185.3 2979.63 ftp06.apple.com tock.gpsclock.c 2 u 12 64 1 68.629 -3153.3 2949.71 It appears that the values like offset -3.200164 is being factored to -3200.1 which I assume is larger than the allowable offset for updating or something. This is really annoying me since the machine that controls time on my network just happens to be the machine with the worse time skew problem. I know, but it was the machine I chose before I found that out. If someone has any information that might be usefull please reply. -Jake jbarrett@amduat.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message