From owner-freebsd-stable Wed Jan 16 23:33:16 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.innovativeinternet.net (ns3.innovativeinternet.net [208.244.165.3]) by hub.freebsd.org (Postfix) with ESMTP id 9A5C637B405 for ; Wed, 16 Jan 2002 23:33:11 -0800 (PST) Received: from pcpsj.pfcs.com (harlan.xecu.net [216.127.150.112]) by mail.innovativeinternet.net (Postfix) with ESMTP id CC9A428C6; Thu, 17 Jan 2002 02:33:02 -0500 (EST) Received: from brown.pfcs.com (brown.pfcs.com [192.52.69.44]) by pcpsj.pfcs.com (Postfix) with ESMTP id 1524AD367; Thu, 17 Jan 2002 01:06:58 -0500 (EST) Received: from localhost.pfcs.com [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 17 Jan 2002 01:06:58 -0500 (EST) To: Peter Jeremy Cc: Gregory Bond , freebsd-stable@FreeBSD.ORG, Harlan.Stenn@pfcs.com Subject: Re: NTP packet routing problem In-Reply-To: Peter Jeremy's (peter.jeremy@alcatel.com.au) message dated Thu, 17 Jan 2002 16:48:11. <20020117164811.T72285@gsmx07.alcatel.com.au> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (20 Minutes to Nikko) (i386-unknown-freebsd2.2.8) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Thu, 17 Jan 2002 01:06:57 -0500 Message-ID: <13699.1011247617@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It might also be the NTP associations - ntpd makes it associations based on the IP of the local machine, and if your PPP link goes down/up and you get a new IP then ntpd will continue to attempt to communicate using its old IP address (association). In this case one of the better answers is to use linkup and linkdown scripts that uses ntpdc(?) to tear down the old association (during linkdown) and brings up a new association during the linkup script. I have no idea if you can avoid this problem by having ntpd bind to a (permanent) local address and then use NAT for the periodic connections. OBTW, if you are using PPP connections for NTP it's probably a good idea to use both the "burst" and "tinker huffpuff 7200" (more or less) things in your ntp.conf file. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message