From: Richard Dicaire <rdicaire1@comcast.net>
To: netfilter@lists.samba.org
Subject: unresolved symbols]
Date: Thu, 30 May 2002 16:55:06 -0400 [thread overview]
Message-ID: <3CF691AA.2090709@comcast.net> (raw)
Hi, I'm getting unresolved symbols from the following under kernel
2.4.18, using iptables v. 1.2.5.
I ran the iptables installation per the INSTALL file, remade the kernel
and modules.
modprobe ip_tables
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_tables.o: unresolved
symbol nf_unregister_sockopt
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_tables.o: unresolved
symbol nf_register_sockopt
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_tables.o: insmod
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_tables.o failed
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_tables.o: insmod
ip_tables failed
I chose modules for all netfilter options, enabled netfilter itself as well.
depmod -a
depmod: *** Unresolved symbols in
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_conntrack.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_queue.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ip_tables.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/ipt_REJECT.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/iptable_filter.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/iptable_mangle.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.18/kernel/net/ipv4/netfilter/iptable_nat.o
Have I missed anything? I have no problems with 2.4.17.
Please respond to me personally, as I'm not on the list, thanks.
next reply other threads:[~2002-05-30 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 20:55 Richard Dicaire [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-03 13:57 Unresolved symbols? Robert L. Harris
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=3CF691AA.2090709@comcast.net \
--to=rdicaire1@comcast.net \
--cc=netfilter@lists.samba.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.