[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netfilter
Subject:    Re: Which one is chosen on multiple default gateway set?
From:       Wei Huang <daviseago () gmail ! com>
Date:       2012-08-23 7:30:21
Message-ID: CAJPS4yZ-dO7Jau6R1V=jBh9xHWjfA-PaiURGzjtGo8TwmDcjSA () mail ! gmail ! com
[Download RAW message or body]

On Thu, Aug 23, 2012 at 2:38 PM, David Miller <davem@davemloft.net> wrote:
> The problem is that when a nexthop becomes unresponsive we need
> to wait for an event to timeout the routing cache entry.
>
> In 3.6.0-rc1 and later, this inconsistent behavior will happen less
> often, because the routing cache has been removed so we will do the
> full default route resolution on every route lookup.  The only problem
> at that point is socket cached routes, those will still need to wait
> for a timeout before the next default gateway will be tried.

Thanks a lot, David!

I'm using 2.6.16. Could you tell me where the code is, that detects
nexthop unresponsive, sends an event, and timeout the cache? Or are
there procs or sysctl to adjust the timer values?

Another thing I found is that the route looking-up seems to update the
routing cache entry. Is that true? In my example in the first mail,
after a while, the default gateway should have been switched to the
second one. If I ping 8.8.8.8 then, the second active gateway should
be used. But instead, if I look for the route first with "ip r get
8.8.8.8", the first inactive gateway will be the result, and it will
be used if I ping now.
Will the route looking-up even influence the behavior? Will there be a
work around way for this?

Thanks,
Wei
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]