Subject: Re: kern/3508 bug: cached ip route and interface up/down.
To: Nick Amato <>
From: Tad Hunt <>
List: tech-net
Date: 11/12/2002 17:14:13
In message <>, you said:
;Unless I'm mistaken, glancing over rtrequest1(), I think the code
;already does this.  When the more specific route is deleted, the
;rt_entry referenced by the cache has its RTF_UP cleared and this
;is noticed in ip_output().

Hmm.  I agree.  It certainly appears as though rtrequest1() marks
the route down, and that ip_output() checks it, and reallocates the
route.  I don't understand why my change fixes the problem then.

Waiting for ip_output() to figure out it needs to use a different route
might cause the code in ip_forward() which decides if it needs to send
a redirect to answer incorrectly.  Even so, I don't see how that could
be the problem.

Unfortunatly, I don't have much more time to spend on this.  I am
not clear on why my change works.