From: Mike Fedyk <mfedyk@matchmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 1+1 HA gateway
Date: Thu, 12 Jul 2001 18:20:18 +0000 [thread overview]
Message-ID: <marc-lartc-99496209104335@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99494925718474@msgid-missing>
On Thu, Jul 12, 2001 at 04:47:57PM +0200, RoMaN SoFt / LLFB!! wrote:
>
> Hi.
>
> I need to setup "one route" to a certain destination network (indeed
> it's another LAN, which I want to connect to, i.e. I'm creating a
> simple VPN). I have 2 possible gateways:
> a) Fast (through an ADSL line via 192.168.7.254. This is a CIPE
> connection)
> b) Slow (through a RDSI line via 192.168.5.3. This is pure PPP)
>
> The situation I'm looking for is having two real routes to the
> destination network (via the fast gateway and the slow one
> respectively) but only the first (úst) one is used in normal
> conditions. The second (=slow) one will only be used in case the first
> breaks (i.e. failover mode).
>
I believe the only way for the kernel to recognize that there has been
a failure, is the ethernet card detecting a line drop. If you can be
sure that when the link goes down that this happens, you won't need
anything else except for the right rules in your routing setup.
If your setup won't do this, you'll need a script that actively checks
for connectivity, or for more complicated setups a routing protocol.
If I'm wrong, someone please let me know.
Mike
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-07-12 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 14:47 [LARTC] 1+1 HA gateway RoMaN SoFt / LLFB!!
2001-07-12 18:20 ` Mike Fedyk [this message]
2001-07-13 16:41 ` Mike Fedyk
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-99496209104335@msgid-missing \
--to=mfedyk@matchmail.com \
--cc=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.