From owner-freebsd-net Tue Nov 20 18: 2:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from rose.niw.com.au (cerberus.apdata.com.au [202.14.95.17]) by hub.freebsd.org (Postfix) with ESMTP id 0D49C37B405 for ; Tue, 20 Nov 2001 18:02:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by rose.niw.com.au (Postfix) with ESMTP id BF4A89721C for ; Wed, 21 Nov 2001 12:32:33 +1030 (CST) Received: by rose.niw.com.au (Postfix, from userid 1000) id 6081F97215; Wed, 21 Nov 2001 12:32:32 +1030 (CST) Date: Wed, 21 Nov 2001 12:32:32 +1030 From: Ian West To: freebsd-net@freebsd.org Subject: expiring cached routes on in_pcb entries. Message-ID: <20011121123232.Q80670@rose.niw.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I have been looking at the code in ip_ouput in relation to a problem I have had with named using the wrong route for talking to forwarders after route changes occur. There is a check for cached routes, and a check for validity, but not as far as I can see a check for expiry. The situation is when the box starts it has a default route, named starts and uses this to talk to try to talk to it's forwarder. (via UDP, but I don't think it matters). Some time later we get a specific route for the subnet on which the forwarder resides via a dialup (tun) interface. While the route tables all update up correctly, and new connections use the direct route, the named connection continues to send packets out via the wrong interface until it is restarted. I am looking at the ip_output routines, but so far cannot see any check for expiry of cached routes ? Can anyone point me in the right direction (or confirm they don't expire unless the route is physically unavailable ?) Thankyou. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message