From owner-freebsd-net@FreeBSD.ORG Wed Feb 7 19:12:53 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0794F16A407; Wed, 7 Feb 2007 19:12:51 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1-3.pacific.net.au [61.8.2.210]) by mx1.freebsd.org (Postfix) with ESMTP id C18CB13C471; Wed, 7 Feb 2007 19:12:50 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.2.163]) by mailout1.pacific.net.au (Postfix) with ESMTP id 750495A1F95; Thu, 8 Feb 2007 06:12:49 +1100 (EST) Received: from besplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (Postfix) with ESMTP id 835EC2740B; Thu, 8 Feb 2007 06:12:48 +1100 (EST) Date: Thu, 8 Feb 2007 06:12:47 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Oleg Bulyzhin In-Reply-To: <20070208043101.K687@besplex.bde.org> Message-ID: <20070208060101.V762@besplex.bde.org> References: <20070125170532.c9c2374hkwk4oc4k@server.yirdis.net> <20070205232800.GA45487@lath.rinet.ru> <20070207003539.I31484@besplex.bde.org> <20070206221857.GA66675@lath.rinet.ru> <20070207193426.P35180@besplex.bde.org> <20070208043101.K687@besplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Robin Gruyters , freebsd-net@FreeBSD.org Subject: Re: [Fwd: Re: bge Ierr rate increase from 5.3R -> 6.1R] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 19:12:54 -0000 On Thu, 8 Feb 2007, I wrote: > 6.2 seems to be missing your fix for the time_uptime time warp -- after > "route delete #remotehost", the negative expire time is slightly less $ > than the uptime under 6.2, but it apparently should be slightly less > than 0 as in ~5.2 and -current. I don't understand the expire times > -- are they really supposed to go negative? The negative expire time seems to be actually the negative of the time since the last down/up, not the negative of the uptime, and this behaviour is the same in ~5.2, 6.2 and -current. 6.2 doesn't need your fix since it still uses time_second. Bruce