From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What failover solution for advanced router ?
Date: Sat, 01 Mar 2003 15:49:56 +0000 [thread overview]
Message-ID: <marc-lartc-104653384631309@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104653007028010@msgid-missing>
Tomasz,
Have you looked at keepalived? It has a rich feature set, is actively
maintained, and can function strictly as a VRRPD.
One intelligent aspect of design allows for two routers to be in active
use each functioning as a backup for the other.
It sounds like your situation is rather complex, but I imagine with some
creativity, you could configure keepalived to your advantage.
http://www.keepalived.org/
http://www.keepalived.org/pdf/UserGuide.pdf
I'd recommend reading the user's guide for some ideas. Given your
description here, I'd suggest reading section X (Case Study) very
carefully.
Good luck,
-Martin
: Hello,
:
: Could someone experienced suggest good solution for failover
: advanced router ?
:
: The router for which I need redundancy is quite complex:
: 1) has 5 interfaces
: 2) uses the same network and the other network IP aliases on some interfaces
: 3) uses bunch of policy routing rules
: 4) uses proxyarp feature on some interfaces
: 5) uses complex iptables setup [propably not important in this issue].
:
: What I need to achieve is basic failover, I do not criticaly need
: transparency failover.
:
: I found some docs about ip_takeover with fake utility but
: propably it has too weak features [and uses old ifconfig]. Also found vrrpd tool but
: I am confused if I can really depend on it for such a "multithread" configuration.
: Finally I consider using Heartbeat with set of scripts for "manual"
: bringing up all interfaces on preconfigured spare router in case of
: primary one fails.
:
: I would be very gratefull for some discuss about proper solution for my
: case.
:
:
: Regards,
: tw
: --
:
: -----------
: ck.eter.tym.pl
:
: _______________________________________________
: LARTC mailing list / LARTC@mailman.ds9a.nl
: http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
:
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-03-01 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 14:50 [LARTC] What failover solution for advanced router ? Tomasz Wrona
2003-03-01 15:49 ` Martin A. Brown [this message]
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-104653384631309@msgid-missing \
--to=mabrown-lartc@securepipe.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.