From: Rusty Russell <rusty@rustcorp.com.au>
To: Andy K <crap.goes.here@gmail.com>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Netfilter development mailing list
<netfilter-devel@lists.netfilter.org>
Subject: Re: Problem: ip_nat_irc.c in kernel 2.6.11.5
Date: Tue, 22 Mar 2005 01:00:01 +1100 [thread overview]
Message-ID: <1111413602.27471.17.camel@localhost.localdomain> (raw)
In-Reply-To: <a17b2e290503200056455a42d6@mail.gmail.com>
On Sun, 2005-03-20 at 00:56 -0800, Andy K wrote:
> Hello,
>
> I recently upgraded my system from kernel 2.6.7 to 2.6.11.5 and have
> found that my DCC transfers no longer work inside my NAT'd network. It
> appears that the ip_nat_irc.c code no longer takes a 'ports'
> parameter, although it did in 2.6.7.
Yes. (CC'd lkml so google gets a sniff of this in future).
Linus, please apply.
Rusty.
Name: Restore ports module parameter for ip_nat_ftp and ip_nat_irc
Status: Tested on 2.6.12-rc1-bk1
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
There is no "ports" parameter for the ip_nat_ftp and ip_nat_irc
modules in 2.6.11: the ports parameter supplied to the
ip_conntrack_ftp/ip_conntrack_irc module defines the ports. It was
unfortunate that we were lazy in the original implementation, and
forced the user to duplicate the arguments.
Even more unfortunate, the removal of the parameter caused autoloading
to break for various setups, with an "Unknown parameter" message. The
solution is to restore the parameter as a dummy, with a polite warning
message that it is no longer neccessary.
Index: linux-2.6.12-rc1-bk1-Netfilter/net/ipv4/netfilter/ip_nat_ftp.c
===================================================================
--- linux-2.6.12-rc1-bk1-Netfilter.orig/net/ipv4/netfilter/ip_nat_ftp.c 2005-03-02 23:28:18.000000000 +1100
+++ linux-2.6.12-rc1-bk1-Netfilter/net/ipv4/netfilter/ip_nat_ftp.c 2005-03-22 00:40:40.000000000 +1100
@@ -170,5 +170,14 @@
return 0;
}
+/* Prior to 2.6.11, we had a ports param. No longer, but don't break users. */
+static int warn_set(const char *val, struct kernel_param *kp)
+{
+ printk(KERN_INFO __stringify(KBUILD_MODNAME)
+ ": kernel >= 2.6.10 only uses 'ports' for conntrack modules\n");
+ return 0;
+}
+module_param_call(ports, warn_set, NULL, NULL, 0);
+
module_init(init);
module_exit(fini);
Index: linux-2.6.12-rc1-bk1-Netfilter/net/ipv4/netfilter/ip_nat_irc.c
===================================================================
--- linux-2.6.12-rc1-bk1-Netfilter.orig/net/ipv4/netfilter/ip_nat_irc.c 2005-03-02 23:28:18.000000000 +1100
+++ linux-2.6.12-rc1-bk1-Netfilter/net/ipv4/netfilter/ip_nat_irc.c 2005-03-22 00:40:33.000000000 +1100
@@ -112,5 +112,14 @@
return 0;
}
+/* Prior to 2.6.11, we had a ports param. No longer, but don't break users. */
+static int warn_set(const char *val, struct kernel_param *kp)
+{
+ printk(KERN_INFO __stringify(KBUILD_MODNAME)
+ ": kernel >= 2.6.10 only uses 'ports' for conntrack modules\n");
+ return 0;
+}
+module_param_call(ports, warn_set, NULL, NULL, 0);
+
module_init(init);
module_exit(fini);
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
parent reply other threads:[~2005-03-21 14:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <a17b2e290503200056455a42d6@mail.gmail.com>]
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=1111413602.27471.17.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=crap.goes.here@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®