From: Max Kellermann <max@duempel.org>
To: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.6] Allow dynamic helper-port assignment
Date: Sun, 13 Feb 2005 18:34:02 +0100 [thread overview]
Message-ID: <20050213173402.GA4688@roonstrasse.net> (raw)
In-Reply-To: <20050213165638.GM20269@sunbeam.de.gnumonks.org>
On 2005/02/13 17:56, Harald Welte <laforge@netfilter.org> wrote:
> Ideally, we would actually have conntrack helpers be iptables targets,
> this way allowing totally dynamic assignemnt. Maybe yet another
> pkttables todo.
Good idea.
The downside is, to use a helper, you have to explicitly configure
it. That is so easy currently - add the helper to the kernel, and it
just works (on the default ports, that is). But that's ok for me.
> Meanwhile, the following patch uses the same mechanism as CLUSTERIP:
>
> Add port 2121 to ftp helper:
> echo "+2121" > /proc/net/ip_conntrack_helper/ftp
>
> Remove port 6669 from irc helper:
> echo "-6669" > /proc/net/ip_conntrack_helper/irc
>
> Show registered ports for amanda helper:
> cat /proc/net/ip_conntrack_helper/amanda
Why don't you use the existing /sys/module/XX/parameters/YY interface?
That includes static modules. We could even use a custom setter
function for the "port" property.
cat /sys/module/ip_conntrack_irc/parameters/ports
That already works, it's just not writable (yet).
> If nobody complains, we should push this for 2.6.12.
*complain*
Why push a solution which will go away soon anyway to the mainstream
kernel? When people understand how to use that change, it's already
gone.
Max
next prev parent reply other threads:[~2005-02-13 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 16:56 [PATCH 2.6] Allow dynamic helper-port assignment Harald Welte
2005-02-13 17:34 ` Max Kellermann [this message]
2005-02-13 22:38 ` Jozsef Kadlecsik
2005-02-14 11:21 ` Harald Welte
2005-02-14 11:59 ` Martijn Lievaart
2005-02-14 12:20 ` Martijn Lievaart
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=20050213173402.GA4688@roonstrasse.net \
--to=max@duempel.org \
--cc=netfilter-devel@lists.netfilter.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.