From owner-freebsd-bugs Tue Jun 5 12:10: 9 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 54D8B37B401 for ; Tue, 5 Jun 2001 12:10:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.3/8.11.3) id f55JA5J24683; Tue, 5 Jun 2001 12:10:05 -0700 (PDT) (envelope-from gnats) Date: Tue, 5 Jun 2001 12:10:05 -0700 (PDT) Message-Id: <200106051910.f55JA5J24683@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: kern/27890: FreeBSD not always seems to take the best route Reply-To: David Malone 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 The following reply was made to PR kern/27890; it has been noted by GNATS. From: David Malone To: Andre Albsmeier Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/27890: FreeBSD not always seems to take the best route Date: Tue, 5 Jun 2001 20:05:57 +0100 On Tue, Jun 05, 2001 at 06:30:14PM +0200, Andre Albsmeier wrote: > The problem is that each time when syslogd on C wants to send > a packet to S, the kernel still uses 1 as router even though > it should send them through 2. After HUPing or restarting > syslogd on C (which means that the UDP socket is closed and > opened again) things are back to normal. This sounds like it is to do with the caching of recently used routes. Does the effect go away if you leave it for a while? Adjusting some of the following sysctls might change how long you have to wait: net.inet.ip.rtexpire net.inet.ip.rtminexpire net.inet.ip.rtmaxcache (Some of the networking people could definitely provide more details.) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message