All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Günter Zimmermann" <guenter@guenter-zimmermann.com>
To: "B. McAninch" <bmcaninch@penson.com>
Cc: Patrick Ahler <patrick@vikus.com>, netfilter@lists.netfilter.org
Subject: Re: Redundant netfilter gateway
Date: Thu, 17 Jun 2004 23:22:10 +0200	[thread overview]
Message-ID: <40D20B82.2040203@guenter-zimmermann.com> (raw)
In-Reply-To: <1087506177.30435.27.camel@wslinux-fractal.penson.com>

Check out OpenBSD with  CARP (the Common Address Redundancy Protocol)  
and pfsync

copied from OpenBSD Site (http://www.openbsd.org/35.html#new):
New tools for filtering gateway failover:

    * CARP (the Common Address Redundancy Protocol) carp(4)
      <http://www.openbsd.org/cgi-bin/man.cgi?query=carp> allows
      multiple machines to share responsibility for a given IP address
      or addresses. If the owner of the address fails, another member of
      the group will take over for it. A discussion of the history of
      CARP can be found here <http://www.openbsd.org/lyrics.html>.
    * Additions to the pfsync(4)
      <http://www.openbsd.org/cgi-bin/man.cgi?query=pfsync> interface
      allow it to synchronise state table entries between two or more
      firewalls which are operating in parallel, allowing stateful
      connections to cross any of the firewalls regardless of where the
      state was initially created.

I think this is the only realy full redundant opensource firewall available.

lg
Günter

B. McAninch schrieb:

>Check out KeepAliveD (keepalived.sourceforge.net)- it uses VRRP for
>failover. It does not, however, provide /stateful/ firewall failover. 
>IIRC, work is (was) being done for Netfilter's own state syncing.
>
>On Thu, 2004-06-17 at 15:52, Patrick Ahler wrote:
>  
>
>>I am looking for info on creating a redundant gateway/firewall. I
>>currently have my network setup with 1 working iptables gateway/firewall
>>and 1 backup gateway. If the first gateway goes down, I change the IP's
>>and spoof the MAC addresses (I change the external MAC address because
>>my internal network is masqueraded through the gateway and just
>>switching the external IP messes with the arp tables on the router...
>>That's a whole other issue though) on the backup gateway and it takes
>>over. This is not redundancy and is dirty. Does anyone have any
>>suggestions on how to do this better?
>>
>>Patrick Ahler
>>Systems Administrator
>>Vikus Corporation 
>>    
>>
>
>  
>


  reply	other threads:[~2004-06-17 21:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 20:52 Redundant netfilter gateway Patrick Ahler
2004-06-17 21:02 ` B. McAninch
2004-06-17 21:22   ` Günter Zimmermann [this message]
2004-06-17 21:12 ` Primero
  -- strict thread matches above, loose matches on Subject: below --
2004-06-17 22:37 Daniel Chemko
2004-06-17 23:50 Patrick Ahler
2004-06-17 23:56 ` Cedric Blancher
2004-06-18  9:56   ` KOVACS Krisztian
     [not found] <20040619042840.20653.69114.Mailman@vishnu.netfilter.org>
2004-06-21 15:12 ` Luis Pacheco
2004-06-22  8:57   ` KOVACS Krisztian

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=40D20B82.2040203@guenter-zimmermann.com \
    --to=guenter@guenter-zimmermann.com \
    --cc=bmcaninch@penson.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=patrick@vikus.com \
    /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.