From owner-freebsd-bugs Wed Jun 6 5:53:42 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from gidgate.gid.co.uk (gid.co.uk [194.32.164.225]) by hub.freebsd.org (Postfix) with ESMTP id B03E737B406; Wed, 6 Jun 2001 05:53:38 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.9.3/8.9.3) id NAA23100; Wed, 6 Jun 2001 13:53:34 +0100 (BST) (envelope-from rb) Message-Id: <4.3.2.7.2.20010606134734.00bab440@gid.co.uk> X-Sender: rbmail@gid.co.uk X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 06 Jun 2001 13:51:39 +0100 To: Ruslan Ermilov , freebsd-bugs@FreeBSD.ORG From: Bob Bishop Subject: Re: kern/27890: FreeBSD not always seems to take the best route In-Reply-To: <200106061240.f56Ce1J14186@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 05:40 06/06/01 -0700, Ruslan Ermilov wrote: >[heavily pruned] > The actual fix would be to notify protocol (from within the > routing code) whenever its routing table is modified. This > notification could then be saved in a variable as timestamp, > and every PCB-cached route could have a similar timestamp as > well, indicating when this "caching" took place. Having > that, ip_output() would "invalidate" cached route if it was > cached before the last routing table modification was done. Alternatively, just have ip_output expire the cached route after a delay. -- Bob Bishop +44 (0)118 977 4017 rb@gid.co.uk fax +44 (0)118 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message