From: hanxin <hanxin@mail.sc.cninfo.net>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Problem loading ip_tables
Date: 14 Feb 2003 10:12:51 +0800 [thread overview]
Message-ID: <1045188778.471.4.camel@mobile_benny> (raw)
In-Reply-To: <200302132151.h1DLpff02343@alegre.cipic.ucdavis.edu>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
Have you "make modules_install" when compile kernel?
在 2003-02-14 五 的 05:51, Zhi-Wei Lu 写道:
> Dear Netfilter/iptables guru,
>
> On a Raidzone OpenNas box, I compiled the kernel (generic 2.4.18 based kernel from
> Raidzone) with netfilter enabled and all iptables stuffs in modules.
>
> However, the kernel fail to load iptables.
>
> Here are some of the error messags:
>
> Flushing all current rules and user defined chains: /lib/modules/2.4.18-i37smp/kernel/net/ipv4/netfilter/ip_tables.o: unresolved symbol nf_unregister_sockopt
> /lib/modules/2.4.18-i37smp/kernel/net/ipv4/netfilter/ip_tables.o: unresolved symbol nf_register_sockopt
> /lib/modules/2.4.18-i37smp/kernel/net/ipv4/netfilter/ip_tables.o: insmod /lib/modules/2.4.18-i37smp/kernel/net/ipv4/netfilter/ip_tables.o failed
> /lib/modules/2.4.18-i37smp/kernel/net/ipv4/netfilter/ip_tables.o: insmod ip_tables failed
> iptables v1.2.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
> Perhaps iptables or your kernel needs to be upgraded.
>
> However, if I do a
>
> cat /proc/ksyms |grep nf_register_sockopt
>
> 802e79a0 nf_register_sockopt_R__ver_nf_register_sockopt
>
> Does anyone encounter similar problem before?
> Thank you.
>
> --
> Zhi-Wei Lu
> CIPIC (Center for Image Processing and Integrated Computing)
> UC Davis Phone: (530)-752-0494
> Davis, CA 95616 Fax: (530)-752-8894
>
>
>
--
-hanxin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-02-14 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 21:51 Problem loading ip_tables Zhi-Wei Lu
2003-02-14 2:12 ` hanxin [this message]
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=1045188778.471.4.camel@mobile_benny \
--to=hanxin@mail.sc.cninfo.net \
--cc=netfilter@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