From: "Antonio Paulo Salgado Forster" <aforster@br.ibm.com>
To: Steve Mickeler <steve@warning.ca>
Cc: Chip Upsal <cupsal@cyberwolf.com>, netfilter@lists.netfilter.org
Subject: RE: Using heartbeat for fall over on IPTables Firewall
Date: Mon, 17 Mar 2003 19:46:22 -0300 [thread overview]
Message-ID: <OF7B17CCF3.AB54FAD5-ON83256CEC.007C125F@LocalDomain> (raw)
a few more reasons:
3) faster takeover;
4) "guaranteed persistence routing path" (from keepalived.org) - the
famous sync_groups
5) interface flags monitoring (through VRRP framework);
6) etc;
7) etc;
IMHO, heartbeat is great for applications servers such as DBs, web servers,
(using) shared disks, etc. For routers, firewalls or load balancers,
keepalived rulez.
Read the documentation at web site...
Forster
Steve Mickeler <steve@warning.ca> on 03/17/2003 07:08:26 PM
To: Chip Upsal <cupsal@cyberwolf.com>
cc: Antonio Paulo Salgado Forster/Brazil/IBM@IBMBR,
netfilter@lists.netfilter.org
Subject: RE: Using heartbeat for fall over on IPTables Firewall
Just off the top of my head:
1) heartbeat is limited to 2 nodes
2) keepalived config is much cleaner and easier to manage.
On Mon, 17 Mar 2003, Chip Upsal wrote:
> in what ways is this better then heartbeat?
>
> -----Original Message-----
> From: Steve Mickeler [mailto:steve@warning.ca]
> Sent: Monday, March 17, 2003 1:39 PM
> To: Antonio Paulo Salgado Forster
> Cc: Chip Upsal; netfilter@lists.netfilter.org
> Subject: Re: Using heartbeat for fall over on IPTables Firewall
>
>
>
> I'll second the vote for keepalived.
>
> Its an amazing tool.
>
> http://www.keepalived.org/
>
>
>
>
> On Mon, 17 Mar 2003, Antonio Paulo Salgado Forster wrote:
>
> >
> > Suggestion: Try using keepalived instead.
> >
> > Regards,
> >
> > Forster
> >
> >
> > Chip Upsal <cupsal@cyberwolf.com>@lists.netfilter.org on 03/17/2003
> > 01:16:46 PM
> >
> > Sent by: netfilter-admin@lists.netfilter.org
> >
> >
> > To: netfilter@lists.netfilter.org, "'linux-ha@muc.de'"
> <linux-ha@muc.de>
> > cc:
> > Subject: Using heartbeat for fall over on IPTables Firewall
> >
> >
> >
> > I am looking to use heartbeat to provide fall over for my iptables
> > firewall.
> > I am looking for those with experience using these tools together.
> >
> > I plan to use RH7.2 on the firewalls.
> >
> > I made some attempts at implementing such a solution but i ran into a
few
> > problems.
> >
> > I would like suggestions on setup of the heartbeat configuration files.
> > Pointers on the iptables startup script. and advice on what kernel
version
> > to use and if any patches need to be applied.
> >
> > Thanks in advance,
> >
> > Chip
> >
> >
> >
> >
> > Chip Upsal
> > SysAdmin
> > CyberWolf Inc
> >
> >
> >
> >
> >
>
next reply other threads:[~2003-03-17 22:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 22:46 Antonio Paulo Salgado Forster [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 21:44 Using heartbeat for fall over on IPTables Firewall Chip Upsal
2003-03-17 22:08 ` Steve Mickeler
2003-03-18 8:02 ` Cedric Blancher
2003-03-17 18:55 Elmshauser, Erik
2003-03-17 16:51 Antonio Paulo Salgado Forster
2003-03-17 20:39 ` Steve Mickeler
2003-03-17 16:16 Chip Upsal
2003-03-17 17:35 ` Marc Cluet
2003-03-17 19:11 ` Kevin Dwyer
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=OF7B17CCF3.AB54FAD5-ON83256CEC.007C125F@LocalDomain \
--to=aforster@br.ibm.com \
--cc=cupsal@cyberwolf.com \
--cc=netfilter@lists.netfilter.org \
--cc=steve@warning.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox