From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [CTNETLINK] Rework conntrack fields dumping logic on events
Date: Thu, 23 Nov 2006 14:56:41 +0100 [thread overview]
Message-ID: <4565A899.3050609@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0611231440070.18293@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> Hi Patrick,
>
> On Thu, 23 Nov 2006, Patrick McHardy wrote:
>
>
>>>The attached patch (on top of Patrick's nf_nat git tree and my patches
>>>sent to this list) implements what I suggested: *do* register the helpers
>>>which are actually assigned by an expectfn. Thus ctnetlink can find them
>>>by name and then fill conntrack with the helper. In order to make sure a
>>>bogus packet can't trigger such helpers, __nf_ct_helper_find had to be
>>>modified. What do you think?
>>
>>This is something needed for userspace-helpers (Harald did some work
>>in this direction), but I can't really think of what it could be used
>>for currently.
>
>
> It is required at conntrack replication if/when the H.323 helper is in
> use. The H.245 helper is currently not registered so there is no
> way to replicate the helper: the name is passed but the other side is
> unable to find the helper on the list of the registered helpers.
Good point :) But instead of overloading tuple semantics a flag would
be cleaner IMO and would allow us to skip them quickly
next prev parent reply other threads:[~2006-11-23 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 1:20 [CTNETLINK] Rework conntrack fields dumping logic on events Pablo Neira Ayuso
2006-11-10 21:09 ` Jozsef Kadlecsik
2006-11-12 23:42 ` Pablo Neira Ayuso
2006-11-14 20:01 ` Jozsef Kadlecsik
2006-11-14 20:50 ` Sven Schuster
2006-11-15 7:43 ` Jozsef Kadlecsik
2006-11-23 13:18 ` Patrick McHardy
2006-11-23 13:46 ` Jozsef Kadlecsik
2006-11-23 13:56 ` Patrick McHardy [this message]
2006-11-23 13:34 ` 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=4565A899.3050609@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@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 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.