From: Phil Oester <kernel@linuxace.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC][PATCH] Per-conntrack timeout target v3
Date: Tue, 27 Nov 2007 16:27:15 -0800 [thread overview]
Message-ID: <20071128002715.GA6555@linuxace.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711280033300.4181@fbirervta.pbzchgretzou.qr>
On Wed, Nov 28, 2007 at 12:34:31AM +0100, Jan Engelhardt wrote:
> Considering TCP only...
>
> If my firewall allows 'NEW' connections (-m conntrack --ctstate NEW) on
> non-SYN packets, what good will xt_TIMEOUT do? If the ct entry times out,
> a new one will be created once the next packet flows.
Correct - in this case, it will not help at all. But many rulesets
require (--state NEW) to be --syn, where this would help.
Phil
next prev parent reply other threads:[~2007-11-28 0:27 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 [this message]
2007-11-28 9:06 ` Patrick McHardy
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=20071128002715.GA6555@linuxace.com \
--to=kernel@linuxace.com \
--cc=jengelh@computergmbh.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 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.