From: Patrick McHardy <kaber@trash.net>
To: Phil Oester <kernel@linuxace.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC][PATCH] Per-conntrack timeout target v3
Date: Wed, 28 Nov 2007 10:06:16 +0100 [thread overview]
Message-ID: <474D2F88.5050707@trash.net> (raw)
In-Reply-To: <20071127190745.GA2080@linuxace.com>
Phil Oester wrote:
> Some further updates/optimizations to my original posting. This version
> handles all protocols now. Anyone besides me think this is useful?
>
> ***
>
> I use a fairly short 2 hour established timeout on firewalls I operate,
> which works fine for most purposes. Occasionally, however, it would
> be nice to have a longer timeout for *certain* types of traffic
> such as SSH or telnet sessions.
>
> So, below find a TIMEOUT target to enable such per-conntrack timeouts.
> Syntax for SSH would be something like:
>
> iptables -A foo -p tcp --dport 22 -j TIMEOUT --timeout 123456
> iptables -A foo -p tcp --dport 22 -j ACCEPT
>
> It could of course also be used to lower the timeouts on some traffic,
> such as HTTP.
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?
next prev parent reply other threads:[~2007-11-28 9:06 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 [this message]
2007-12-17 21:20 ` Phil Oester
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=474D2F88.5050707@trash.net \
--to=kaber@trash.net \
--cc=kernel@linuxace.com \
--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 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.