From: Patrick McHardy <kaber@trash.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: [NETFILTER]: xt_hashlimit: fix ip6tables dependency
Date: Wed, 31 Jan 2007 01:39:47 +0100 [thread overview]
Message-ID: <45BFE553.2070206@trash.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 162 bytes --]
Hi Dave,
while testing similar combinations that lead to the H.323 linker
error, I noticed this problem with xt_hashlimit.
Please also apply to 2.6.20. Thanks.
[-- Attachment #2: x --]
[-- Type: text/plain, Size: 1191 bytes --]
[NETFILTER]: xt_hashlimit: fix ip6tables dependency
IP6_NF_IPTABLES=m, CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=y results in a
linker error since ipv6_find_hdr is defined in ip6_tables.c. Fix similar
to Adrian Bunk's H.323 conntrack patch: selecting ip6_tables to be build
as module requires hashlimit to be built as module as well.
Signed-off-by: Patrick McHardy <kaber@trash.net>
---
commit 25dfa116b43b65d9e3bb5e89d392b6ebd1d00ec7
tree c4fa2b5e88eca77a237ffd3cd37419df45cb6ef7
parent 9c13a2e187957e0656eb458ca1251bd1b79aebaa
author Patrick McHardy <kaber@trash.net> Wed, 31 Jan 2007 01:35:02 +0100
committer Patrick McHardy <kaber@trash.net> Wed, 31 Jan 2007 01:35:02 +0100
net/netfilter/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/netfilter/Kconfig b/net/netfilter/Kconfig
index cd10e44..2a2bcb3 100644
--- a/net/netfilter/Kconfig
+++ b/net/netfilter/Kconfig
@@ -628,7 +628,7 @@ config NETFILTER_XT_MATCH_TCPMSS
config NETFILTER_XT_MATCH_HASHLIMIT
tristate '"hashlimit" match support'
- depends on NETFILTER_XTABLES
+ depends on NETFILTER_XTABLES && (IP6_NF_IPTABLES || IP6_NF_IPTABLES=n)
help
This option adds a `hashlimit' match.
next reply other threads:[~2007-01-31 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 0:39 Patrick McHardy [this message]
2007-01-31 5:36 ` [NETFILTER]: xt_hashlimit: fix ip6tables dependency David Miller
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=45BFE553.2070206@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--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.