From: Phil Oester <kernel@linuxace.com>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH] Module aliases for xt_iprange
Date: Mon, 12 May 2008 10:42:46 -0700 [thread overview]
Message-ID: <20080512174246.GA28222@linuxace.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
Using iptables 1.3.8 with kernel 2.6.25, rules which include '-m iprange'
don't automatically pull in xt_iprange module. Below patch adds module
aliases to fix that. Patch against latest -git, but seems like a good
candidate for -stable also.
Phil
Signed-off-by: Phil Oester <kernel@linuxace.com>
[-- Attachment #2: patch-xt_range-alias --]
[-- Type: text/plain, Size: 448 bytes --]
--- linux-2.6.25.i686/net/netfilter/xt_iprange.c.orig 2008-05-12 12:25:55.000000000 -0400
+++ linux-2.6.25.i686/net/netfilter/xt_iprange.c 2008-05-12 12:23:55.000000000 -0400
@@ -179,3 +179,5 @@
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>, Jan Engelhardt <jengelh@computergmbh.de>");
MODULE_DESCRIPTION("Xtables: arbitrary IPv4 range matching");
+MODULE_ALIAS("ipt_iprange");
+MODULE_ALIAS("ip6t_iprange");
next reply other threads:[~2008-05-12 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 17:42 Phil Oester [this message]
2008-05-12 17:55 ` [PATCH] Module aliases for xt_iprange 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=20080512174246.GA28222@linuxace.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox