netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: RFC: netfilter: xtables: add CT target
Date: Tue, 19 Jan 2010 11:40:17 +0100	[thread overview]
Message-ID: <4B558C11.9020607@trash.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1001191115160.3138@blackhole.kfki.hu>

Jozsef Kadlecsik wrote:
> On Tue, 19 Jan 2010, Patrick McHardy wrote:
> 
>> The attached two patches add a 'CT' target to specify parameters
>> used during conntrack creation. This can be used to manually attach
>> a helper to a connection. A couple of patches I'm still working
>> on will additionally use this for the "conntrack zones" classification.
>>
>> I'm wondering if anyone has further ideas of parameters that might
>> make sense to support. We could for example move parameters like
>> sip_direct_signalling and sip_direct_media into the helper structure
>> and allow to set them dynamically for each connection. Or perhaps
>> selectively enable netlink events.
> 
> Selectively enabling netlink events (not only per connection but per event 
> type) would be cool! Last year I used the CONNMARK target for that purpose 
> - maybe it fits better to the CT target.

I think it would be a good fit since you probably would want to specify
the events to be delivered before the conntrack is created.

Adding an event mask to the ecache extension also looks unproblematic.
You could then use a rule like this:

iptables -t raw .. -j CT --ctevents new,related,protoinfo,helper

or something like that. Are the existing event types fine grained
enough for this? Also, should the CT target override the global
sysctl setting?

  reply	other threads:[~2010-01-19 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19  9:05 RFC: netfilter: xtables: add CT target Patrick McHardy
2010-01-19  9:55 ` Jan Engelhardt
2010-01-19 10:19   ` Patrick McHardy
2010-01-19 10:27 ` Jozsef Kadlecsik
2010-01-19 10:40   ` Patrick McHardy [this message]
2010-01-19 12:06     ` Patrick McHardy
2010-01-19 16:03       ` Patrick McHardy
2010-01-20  9:19     ` Jozsef Kadlecsik
2010-01-20  9:37       ` Patrick McHardy
2010-01-20  9:50         ` Jozsef Kadlecsik
2010-01-20  9:52           ` 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=4B558C11.9020607@trash.net \
    --to=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).