From owner-freebsd-hackers Tue Sep 16 23:51:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA23258 for hackers-outgoing; Tue, 16 Sep 1997 23:51:20 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA23247 for ; Tue, 16 Sep 1997 23:51:16 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA19697 for hackers@FreeBSD.ORG; Wed, 17 Sep 1997 08:51:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA25884; Wed, 17 Sep 1997 08:20:39 +0200 (MET DST) Message-ID: <19970917082039.MU62170@uriah.heep.sax.de> Date: Wed, 17 Sep 1997 08:20:39 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: Kernel clock runs inaccurately References: <199709080124.JAA14004@tao.sinanet.com.tw> <19970908081010.DS04250@uriah.heep.sax.de> <199709102025.WAA02815@bitbox.follo.net> <19970911064231.JG62790@uriah.heep.sax.de> <199709170431.GAA29657@bitbox.follo.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199709170431.GAA29657@bitbox.follo.net>; from Eivind Eklund on Sep 17, 1997 06:31:55 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Eivind Eklund wrote: > I was suggesting _suppressing_ dial-out when xntpd tried to send a > packet. Ie, something similar to the dial filter in IIJ-PPP, ignoring > NTP-packets. I figured this. Anyway, i think i'm now more accurate for less costs. The DCF-77 clock is hanging upon a machine that has a rather well system clock already. It succeeds to convert the timecode information about 50 % of the time, and runs with stratum 1 then. For the remaining 50 %, the local system clock takes over at stratum 4. This should give the entire network an accuracy of better than a few hundred milliseconds, and that's all what we need. > BTW: What kind of setup are you running to get <2s setup time? I'm > consistently ending up at 4-5s, having tried with different external > TAs, ISDN-adapters, PPP-implementations and portmasters. As Greg mentioned, public network connection setup time here is usually between 1 and 2 seconds. FreeBSD's SyncPPP (/sys/net/sppp*) is now at about another second or two in negotiating (dependent on the convergency behaviour of the negotiated options), with an ISDN router on the other end manufactured by Conware (who you probably don't know :). The Ascend P50 for our Internet connection is in the same area, the ISP is using an Ascend Max on the other end. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)