From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: What's required for a stateful firewall + ipvs in 2.6 kernel?
Date: Tue, 23 Sep 2008 15:31:37 -0500 [thread overview]
Message-ID: <48D95229.8040705@riverviewtech.net> (raw)
In-Reply-To: <48D8C06F.6030101@netfilter.org>
On 09/23/08 05:09, Pablo Neira Ayuso wrote:
> The last time that I had a look at the antefacto patch it look to me
> like a hack. IIRC, the problem is the LVS design (at least time ago
> when I had a look at it) as it bypasses the network stack. This
> screws up the possibility of having stateful firewalling and LVS.
I can offer a recent confirmation (with in the last three months) that
LVS does indeed still interfere with firewalling.
Grant. . . .
prev parent reply other threads:[~2008-09-23 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 23:47 What's required for a stateful firewall + ipvs in 2.6 kernel? Brian Ghidinelli
2008-09-10 15:16 ` Grant Taylor
2008-09-10 17:00 ` Brian Ghidinelli
2008-09-10 17:03 ` Grant Taylor
2008-09-23 10:09 ` Pablo Neira Ayuso
2008-09-23 20:31 ` Grant Taylor [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=48D95229.8040705@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox