From: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: LVS Devel <lvs-devel@vger.kernel.org>
Subject: Re: [PATCH] Runtime interception method switch
Date: Wed, 16 Jan 2008 12:16:19 +0100 [thread overview]
Message-ID: <478DE783.5070203@tis.icnet.pl> (raw)
In-Reply-To: <20080116075044.GA19249@verge.net.au>
Simon Horman wrote:
> On Tue, Jan 15, 2008 at 05:13:14AM -0800, Joseph Mack NA3T wrote:
>> What side effects might there be? Are they worse than not being able to
>> NAT packets emerging from a director?
>
> I'm not sure, and thats what concerns me.
>
> For starters could we clarify that the patch in question is the
> following one by Janusz Krzysztofik?
>
> Also can I clarify that the aim is to be able to SNAT LVS-DR
> connections ...
Hi,
I can confirm what I have already said before: this patch works for me
(now for over two years) without any unexpected side effects. The only
side effect I can see is that all LVS-DR incoming packets go through
conntrack, even if you do not intend to SNAT them. That could present
excessive load on ancient hardware, but one can just unload conntrack
modules, or turn connection tracking off for specific traffic with
PREROUTING raw hook rules.
However, I think this patch should be considered, if at all, as a
temporary solution.
Thanks,
Janusz
PS. I am still busy with a different project, but subscribed to lvs-devel.
next prev parent reply other threads:[~2008-01-16 11:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 15:12 [PATCH] Runtime interception method switch Raphael Vallazza
2008-01-13 17:59 ` Joseph Mack NA3T
2008-01-14 8:39 ` Raphael Vallazza
2008-01-14 9:42 ` Joseph Mack NA3T
2008-01-15 8:25 ` Simon Horman
2008-01-15 13:13 ` Joseph Mack NA3T
2008-01-16 7:50 ` Simon Horman
2008-01-16 11:16 ` Janusz Krzysztofik [this message]
2008-01-16 11:28 ` Raphael Vallazza
2008-01-18 8:52 ` Simon Horman
2008-01-16 15:09 ` Joseph Mack NA3T
2008-01-18 8:58 ` Simon Horman
2008-01-18 13:12 ` Joseph Mack NA3T
2008-01-15 8:20 ` Simon Horman
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=478DE783.5070203@tis.icnet.pl \
--to=jkrzyszt@tis.icnet.pl \
--cc=lvs-devel@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 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.