From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Patrick McHardy <kaber@trash.net>, netfilter-devel@vger.kernel.org
Subject: Re: The glorious NFCT "none" helper
Date: Mon, 23 May 2011 18:13:07 +0200 [thread overview]
Message-ID: <4DDA8793.7010203@netfilter.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1105231755550.18360@frira.zrqbmnf.qr>
On 23/05/11 17:59, Jan Engelhardt wrote:
> On Monday 2011-05-23 17:47, Pablo Neira Ayuso wrote:
>
>> On 23/05/11 16:29, Patrick McHardy wrote:
>>> On 19.05.2011 00:21, Jan Engelhardt wrote:
>>>> Hej,
>>>>
>>>>
>>>> While working with a customer setup, I came up with this funny idea
>>>> of plugging a no-op NFCT helper in to workaround some nfct_ftp
>>>> problem. Besides that, it may also be used to simply skip helping and
>>>> save cycles. See the patch's message for details - I'd love to hear
>>>> something about it.
>>>>
>>>> (NB: nf_nat_ftp was loaded, but not used when connecting between netA
>>>> and netB.)
>>>
>>> Wouldn't a flag to the CT target to skip the helper lookup work as well?
>>
>> Indeed.
>
> Yes, but how would xt_CT.ko convey to NFCT then that no helper is
> supposed to be used? Calling nf_ct_helper_ext_add, but then leave help
> at NULL?
You can attach a template conntrack in the raw table with the CT target.
That template should have some status flag set to skip helper
allocation/assignation.
I sent a patch to Patrick to fix some problem with the current userspace
expectation approach, the idea would be similar.
next prev parent reply other threads:[~2011-05-23 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 22:21 The glorious NFCT "none" helper Jan Engelhardt
2011-05-18 22:21 ` [PATCH] netfilter: the "none" conntrack helper module Jan Engelhardt
2011-05-23 14:29 ` The glorious NFCT "none" helper Patrick McHardy
2011-05-23 15:47 ` Pablo Neira Ayuso
2011-05-23 15:59 ` Jan Engelhardt
2011-05-23 16:13 ` Pablo Neira Ayuso [this message]
2011-05-24 7:06 ` Patrick McHardy
2011-05-24 19:03 ` Pablo Neira Ayuso
2011-06-07 10:23 ` Patrick McHardy
2011-06-07 11:09 ` Patrick McHardy
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=4DDA8793.7010203@netfilter.org \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netfilter-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.