From owner-freebsd-bugs Fri Mar 29 12:20:10 2002 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 2BC3337B41B for ; Fri, 29 Mar 2002 12:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2TKK4321212; Fri, 29 Mar 2002 12:20:04 -0800 (PST) (envelope-from gnats) Date: Fri, 29 Mar 2002 12:20:04 -0800 (PST) Message-Id: <200203292020.g2TKK4321212@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: William Carrel Subject: Re: kern/16318: Fix for wrong interface when adding new routes Reply-To: William Carrel 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/16318; it has been noted by GNATS. From: William Carrel To: freebsd-gnats-submit@freebsd.org Cc: william.a@carrel.org Subject: Re: kern/16318: Fix for wrong interface when adding new routes Date: Fri, 29 Mar 2002 12:18:30 -0800 I can confirm that this problem still occurs in RELENG_4. I'm not sure if the patch I provided is still valid. To reproduce on a system with two interfaces... ifconfig if0 10.0.1.0 -netmask 255.255.255.0 ifconfig if1 10.0.2.0 -netmask 255.255.255.0 route add 10.0.2.1 -interface if0 route add default 10.0.2.1 netstat -rnfinet will show that the default route points toward if1 even though a static route for 10.0.2.1 shows it should be going to if0. Since the route add default won't take an -interface argument it gets a little difficult to handle. The patch provided against the ancient version fixed it there. I'm not sure how much that code has changed in the past year or two. p.s. apologies for the late reply To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message