Mike Silbersack writes:
> > I have seen the problem occur on two different machines, one is running
> > code 4.3-STABLE FreeBSD 4.3-STABLE #0: Thu May 10 15:13:04 CST 2001
> > the other is 4.3-STABLE FreeBSD 4.3-STABLE #0: Mon May 28 16:10:27 CST
> > 2001 Both machines showed named requests taking
On Wed, 21 Nov 2001, Ian West wrote:
> I have seen the problem occur on two different machines, one is running
> code 4.3-STABLE FreeBSD 4.3-STABLE #0: Thu May 10 15:13:04 CST 2001
> the other is 4.3-STABLE FreeBSD 4.3-STABLE #0: Mon May 28 16:10:27 CST
> 2001 Both machines showed named requests
On Tue, Nov 20, 2001 at 08:45:31PM -0600, Mike Silbersack wrote:
>
> On Wed, 21 Nov 2001, Ian West wrote:
>
> > 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
On Wed, 21 Nov 2001, Ian West wrote:
> 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
< said:
> 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 ?)
Routes which are in use do not have timers on them, and the
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
