From: Arthur van Leeuwen arthurvl@sci.kun.nl
To: lartc@vger.kernel.org
Subject: [LARTC] 2 default gw in redhat 6.2
Date: Thu, 01 Feb 2001 21:35:13 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416944@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416935@msgid-missing>
<PRE>On Thu, 1 Feb 2001, Rene 'Lynx' Pfeiffer wrote:
><i> On Thu, 1 Feb 2001, Arthur van Leeuwen wrote:
</I>><i>
</I>><i> > On Thu, 1 Feb 2001, bert hubert wrote:
</I>><i> >
</I>><i> > > Linux is supposed to have something called 'dead gateway detection'
</I>><i> >
</I>><i> > Which it doesn't use when there's a multipath default route. Now, that isn't
</I>><i> > technically the case here, so that shouldn't be the problem here.
</I>><i>
</I>><i> Does this mean that Linux automatically detects a failed default
</I>><i> route and takes the second one if I configure two default routes?
</I>
No, it means the exact opposite. If you configure two default routes
Linux will randomly multiplex outgoing connections over the two routes.
As opposed to the case of a single route it will not even *try* to do
dead gateway detection on these routes anymore. Yes, I do think that
behaviour is silly. However, I haven't thought of a better way to do
it yet.
Doei, Arthur.
--
/\ / | <A HREF="mailto:arthurvl@sci.kun.nl">arthurvl@sci.kun.nl</A> | Work like you don't need the money
/__\ / | A friend is someone with whom | Love like you have never been hurt
/ \/__ | you can dare to be yourself | Dance like there's nobody watching
</PRE>
next prev parent reply other threads:[~2001-02-01 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 19:49 [LARTC] 2 default gw in redhat 6.2 fabian1 fabian1
2001-02-01 21:06 ` bert
2001-02-01 21:18 ` Arthur
2001-02-01 21:29 ` Rene
2001-02-01 21:35 ` Arthur [this message]
2001-02-01 23:07 ` Rene
2001-02-02 9:32 ` Arthur
2001-02-02 13:44 ` Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-98373940416944@msgid-missing \
--to=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.