From: Patrick McHardy <kaber@trash.net>
To: Phil Oester <kernel@linuxace.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
netfilter-devel@vger.kernel.org
Subject: Re: [RFC][PATCH] Per-conntrack timeout target v3
Date: Fri, 04 Jan 2008 15:23:11 +0100 [thread overview]
Message-ID: <477E414F.9080208@trash.net> (raw)
In-Reply-To: <20071217220100.GA24118@linuxace.com>
Phil Oester wrote:
> On Mon, Dec 17, 2007 at 10:28:49PM +0100, Jan Engelhardt wrote:
>>> 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
>> BTW, the helper code is said to already do that (man iptables):
>>
>> --helper ftp-2121
>
> Actually that's for the helper _match_, so you could for instance
> match packets which are part of a helper configured on a non-standard
> port via module parameter. So this is different, in that it would
> allow you to specify non-standard ports at runtime.
One of the really nice things about this is that it makes helpers
explicit. I never liked the automatic tracking very much since
helpers effectively change your ruleset, and there isn't even a
way to disable them selectively besides blocking connections
completely.
next prev parent reply other threads:[~2008-01-04 14:26 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
2007-12-17 21:28 ` Jan Engelhardt
2007-12-17 22:01 ` Phil Oester
2008-01-04 14:23 ` Patrick McHardy [this message]
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=477E414F.9080208@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--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.