From: Phil Oester <kernel@linuxace.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC][PATCH] Per-conntrack timeout target v3
Date: Mon, 17 Dec 2007 13:20:10 -0800 [thread overview]
Message-ID: <20071217212010.GA23837@linuxace.com> (raw)
In-Reply-To: <474D2F88.5050707@trash.net>
On Wed, Nov 28, 2007 at 10:06:16AM +0100, Patrick McHardy wrote:
> I think the patch is useful, but I wonder how long it will take until
> people want to override timeouts for other connection states. I'm
> also looking for a way to pass parameters for new connections to
> helpers (most of the things that are currently module parameters),
> so maybe we could generalize this to a conntrack parameter target?
In thinking about this, it seems like a HELPER target would be
useful, for instance if some random FTP server ran on a non-standard
port and we wanted the FTP helper to be used. Something like:
-s X -p 210 -j HELPER --helper ftp
Or did you have something else in mind, such as being able to
change the _global_ ports in use by the FTP helper? (or both?)
I suppose we could allow adjustment of other timeouts by
having multiple arguments to -j TIMEOUT, such as --syn_sent,
--syn_recv, etc. though the check() becomes more complicated
between the various protos.
Phil
next prev parent reply other threads:[~2007-12-17 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 19:07 [RFC][PATCH] Per-conntrack timeout target v3 Phil Oester
2007-11-27 23:34 ` Jan Engelhardt
2007-11-28 0:27 ` Phil Oester
2007-11-28 9:06 ` Patrick McHardy
2007-12-17 21:20 ` Phil Oester [this message]
2007-12-17 21:28 ` Jan Engelhardt
2007-12-17 22:01 ` Phil Oester
2008-01-04 14:23 ` Patrick McHardy
2008-01-04 14:21 ` 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=20071217212010.GA23837@linuxace.com \
--to=kernel@linuxace.com \
--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 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).