From owner-freebsd-net Sat May 9 22:13:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15212 for freebsd-net-outgoing; Sat, 9 May 1998 22:13:35 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15203 for ; Sat, 9 May 1998 22:13:28 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (localhost.softweyr.com [127.0.0.1]) by softweyr.com (8.8.8/8.8.7) with ESMTP id XAA09071; Sat, 9 May 1998 23:13:20 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <3555376F.7FBAA205@softweyr.com> Date: Sat, 09 May 1998 23:13:19 -0600 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Julian Elischer CC: freebsd-net@FreeBSD.ORG Subject: Re: Have I left something out? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian Elischer wrote: > > On Thu, 7 May 1998, Joao Carlos Mendes Luis wrote: > > > #define quoting(Richard Wackerbarth) > > // However on the machine which has the point of failure, even though the > > // interface is marked "down", it still insists that that is THE route to > > // any machines which would be on that net. > > This is a known bug and there are fixes for it floating around > but none are really 'correct' > "The Right Way" to fix it is with a function that walks the route table and deletes all the routes whose ifp points to the ifnet being detached. I haven't had time to poke into the FreeBSD sources yet. If nobody else gets this, I'll look into it as soon as I get my plate cleared at work a bit. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message