From: Arthur van Leeuwen arthurvl@sci.kun.nl
To: lartc@vger.kernel.org
Subject: [LARTC] Advanced routing question.
Date: Tue, 16 Jan 2001 10:17:57 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416889@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416884@msgid-missing>
<PRE>On Tue, 16 Jan 2001, Paul Wouters wrote:
><i> On Tue, 16 Jan 2001, Arthur van Leeuwen wrote:
</I>><i>
</I>><i> > > 2> Setup a fail over method so that if either internet connection were
</I>><i> > > to fail it would start routing all outbound traffic over that link.
</I>><i>
</I>><i> > Yes. Linux using Advanced Routing can be used to solve these problems, but
</I>><i> > for problem 2: at the IP level there is no way to figure out wether or not a
</I>><i> > link is down. Ofcourse, you can approximate problem 2, but you have no
</I>><i> > guarantees that the problem lies with the link and not with the servers you
</I>><i> > test your connectivity against, or the infrastructure to those servers
</I>><i> > beyond your direct link.
</I>><i>
</I>><i> What happens if you use the bonding driver and one of the two parts of the
</I>><i> link goes down? Is that transparent?
</I>
What bonding driver? And no, a link failing is *not* transparent. It will
lead to intermittent connectivity problems, as the multipath routing code
will randomly keep selecting the failed link as well as the one still working.
You will have to do active monitoring. Yes, polling. Unfortunately. Let's
all hope for IPv6 and true NUD...
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-01-16 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 23:50 [LARTC] Advanced routing question Daniel
2001-01-16 9:38 ` Arthur
2001-01-16 10:13 ` Paul
2001-01-16 10:17 ` Arthur [this message]
2001-01-16 14:56 ` Daniel
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-98373940416889@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.