Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Kovacs Krisztian <hidden@balabit.hu>
To: jimm@simutronics.com
Cc: "LinuxVirtualServer.org users mailing list."
	<lvs-users@linuxvirtualserver.org>,
	netfilter@lists.samba.org
Subject: Re: LVS and fault-tolerant Firewall.
Date: Wed, 17 Sep 2003 10:09:35 +0200	[thread overview]
Message-ID: <3F6816BF.4040006@balabit.hu> (raw)
In-Reply-To: <NDBBKABJBJCIJNAELLKEIECJJDAA.jimm@simutronics.com>


   Hi,

James Miller wrote:
> Yes, but you can not run iptables/netfilter and maintain connection tracking
> with keepalived(vrrp).. so if you fail over, established/related traffic
> will not be known to .
> 
> For some folks this isn't an issue.  For me is a show-stopper.  I'm sure
> there are good reasons why the netfilter folks can't come up with conntrack
> state-sharing mechanism.

   This is not true. Harald has published a paper last year at OLS2002, 
which gives an overview how connection tracking failover could be 
implemented for Netfilter. There are no theoretical problems with the 
approach, I've created some proof-of-concept code this spring. However, 
it's far from being usable in a real-world environment, at the moment, and 
this is the primary reason it has not been released to the public yet. You 
can get slightly more information from my presentation at the second 
Netfilter Workshop, available in OpenOffice.org Impress format at 
http://home.sch.bme.hu/~piglet/nf-ha/nfws_ha.sxi

-- 
   Regards,
     Krisztian KOVACS



  reply	other threads:[~2003-09-17  8:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1063747546.3f677fdab3817@webmail.datafx.com.au>
2003-09-16 22:41 ` LVS and fault-tolerant Firewall James Miller
2003-09-17  8:09   ` Kovacs Krisztian [this message]
2003-09-17  9:25   ` Joseph Mack

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=3F6816BF.4040006@balabit.hu \
    --to=hidden@balabit.hu \
    --cc=jimm@simutronics.com \
    --cc=lvs-users@linuxvirtualserver.org \
    --cc=netfilter@lists.samba.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