From owner-freebsd-net Sun May 10 20:42:19 1998
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id UAA28690
for freebsd-net-outgoing; Sun, 10 May 1998 20:42:19 -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 UAA28658
for <freebsd-net@FreeBSD.ORG>; Sun, 10 May 1998 20:42:05 -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 VAA10662;
Sun, 10 May 1998 21:41:58 -0600 (MDT)
(envelope-from wes@softweyr.com)
Message-ID: <35567386.7E493152@softweyr.com>
Date: Sun, 10 May 1998 21:41:58 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr llc
X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386)
MIME-Version: 1.0
To: dg@root.com
CC: Julian Elischer <julian@whistle.com>, freebsd-net@FreeBSD.ORG
Subject: Re: Have I left something out?
References: <199805100532.WAA16228@implode.root.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
David Greenman wrote:
> >"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.
>
> This is normally done by the routing daemon. In the case of routed, it
> scans the list of interfaces periodically for changes. For gated, it has
> a socket open for up/down change events and takes care of business as soon
> as it sees the change. I'm inclined to think that this functionality
> should stay in the route daemon where it has always been since deleting
> the routes to the interface may not be the correct course of action.
There was some naive code in the 4.2-based VxWorks stack that would
actually attempt to route code through these "dangling" ifp pointers.
This apparently led to occasional system crashes. We should at least
make certain this is not the case in the FreeBSD code.
Our IP routing team decided it was never appropriate to leave routes
through detached interfaces in the current routing table. Your
mileage may vary.
--
"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