netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: RFC: netfilter: xtables: add CT target
Date: Tue, 19 Jan 2010 11:19:42 +0100	[thread overview]
Message-ID: <4B55873E.3030308@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1001191047480.13020@obet.zrqbmnf.qr>

Jan Engelhardt wrote:
> On Tuesday 2010-01-19 10:05, 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.
> 
> Phil Oester/Pablo had proposed an earlier conntrack target to do just 
> that.
> 
> [3] 
> http://thread.gmane.org/gmane.comp.security.firewalls.netfilter.devel/21499
> (Can't find Pablo's update to that)

We could use the CT target to specify a fixed timeout, but since
it is only used for creating the conntrack entry, the timeouts
wouldn't be refreshed for received packets. This doesn't sound
very useful. Of course the target could also modify existing
connections, but that doesn't fit into the concept very well.

  reply	other threads:[~2010-01-19 10:19 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 [this message]
2010-01-19 10:27 ` Jozsef Kadlecsik
2010-01-19 10:40   ` Patrick McHardy
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=4B55873E.3030308@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@medozas.de \
    --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).