All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Patrick McHardy <kaber@trash.net>
Subject: Re: [CTNETLINK] Rework conntrack fields dumping logic on events
Date: Mon, 13 Nov 2006 00:42:15 +0100	[thread overview]
Message-ID: <4557B157.6010205@netfilter.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0611102151300.26087@blackhole.kfki.hu>

Hi Jozsef,

Jozsef Kadlecsik wrote:
> On Fri, 10 Nov 2006, Pablo Neira Ayuso wrote:
> 
>> This patch also replace IPCT_HELPINFO by IPCT_HELPER since we want to
>> track the helper assignation process, not the changes in the private
>> information held by the helper.
> 
> Actually, how it is solved to pass the setting of dynamically assigned 
> (i.e. currently not registered) helpers? What about registering such 
> helpers with non-matching address/proto/port parameters?

I'm unsure that I understand the question. Currently ctnetlink cannot
assign a helper that is not registered. Therefore, in order to register
a helper with non-matching parameter, wouldn't we need a new parameter
at modprobe stage? Perhaps some kind of userspace tool to manage helper
matching parameters could be interesting.

-- 
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris

  reply	other threads:[~2006-11-12 23:42 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 [this message]
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
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=4557B157.6010205@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.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.