Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Julian Gomez <kluivert@tm.net.my>
To: netfilter@lists.netfilter.org
Subject: Re: H/A
Date: Mon, 26 May 2003 17:59:09 +0800	[thread overview]
Message-ID: <20030526095909.GC1568@floyd> (raw)
In-Reply-To: <27597.200.48.226.214.1053917112.squirrel@www.netfids.com>

On Sun, May 25, 2003 at 09:45:12PM -0500, g_netfilter@netfids.com spoke thusly:

>Hi friends, I have some boxes running iptables and i works well. But now I
>need to configure a failover solution, please could you give me some links
>to start reading? I need to consider Netfilter/Iptables and FreeSwan in
>the same box and with a failover configuration.

A few things you need to clarify :

	a) What are the failover criteria ? Does the other box need to
	   maintain full state, or can you accept that all connections will
	   die for the moment, and can be re-established with the new
	   master server ?

           If state is required, iptables2 should contain failover
	   capability according to some previous posts by Harald. There was
	   some experimental work being done by someone, in regards to
	   exporting the entries out (you'll have to check the archives for
	   details). I'm not sure how you'll get freeswan to play nice
	   though.

	b) If you merely want dumb failover, then google around for VRRP.
	   But understand the drawbacks in each circumstance.


  reply	other threads:[~2003-05-26  9:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26  2:45 H/A g_netfilter
2003-05-26  9:59 ` Julian Gomez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-26  2:55 H/A George Vieira
2003-05-26  3:49 ` H/A g_netfilter
2003-05-26 21:47 H/A George Vieira
2003-05-27 10:09 ` H/A Julian Gomez
2003-05-27 11:34 H/A George Vieira

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=20030526095909.GC1568@floyd \
    --to=kluivert@tm.net.my \
    --cc=netfilter@lists.netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox