From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] iptables
Date: Tue, 30 Aug 2005 09:42:03 +0800 [thread overview]
Message-ID: <1125366124.20471.57.camel@localhost> (raw)
In-Reply-To: <000f01c5acf3$ab2f4780$0501a8c0@croatus>
iptables has an "extensions" use flag which you may or may not need
depending on what the firestarter scripts do.
After installing modules, you need to run modules-update to get the
modules database sorted out. This may fix the symbol error. In some
cases, you need to reboot into the new kernel as the symbols in the
running kernel and new modules may be out of sync.
BillK
On Mon, 2005-08-29 at 19:44 -0400, John Dangler wrote:
> I emerged firestarter (during which I got iptables), and forgot that I
> didn't have iptables emerged prior. I went into the kernel and selected (as
> the doc I found suggests) all of the options as modules under iptables. (The
> doc also says that if they are compiled as modules, I didn't need to
> reboot).
> I did add iptables to /etc/modules.autoload.d/kernel-2.6 (for subsequent
> rebooting).
>
> modprobe ip_tables results in:
> FATAL: Error inserting ip_tables
> (/lib/modules/2.6.12-gentoo-r9/kernel/net/ipv4/netfilter/ip_tables.ko):
> Unknown symbol in module, or unknown parameter.
>
> dmesg produces -
> ip_tables: disagrees about version of symbol skb_copy_files
> ip_tables: Unknow symbol skb_copy_bits
> ip_tables: Unknown symbol nf_register_sockopt
> ip_tables: ip_tables: Unknown symbol nf_unregister_sockopt
> ip_tables: Unknown symbol nf_unregister_sockopt
>
> (I just found another doc that says to ONLY modprobe IF you haven't built
> this as a module)
> DOH!
>
> I went back into the kernel config and removed all but the essential options
> for iptables... (just iptables module) and rebuilt the kernel
>
> A reboot (aside from losing my wireless), produced an error on boot loading
> iptables.
> no other text in dmesg points to the problem.
>
> John D
>
>
>
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-30 2:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 23:44 [gentoo-user] iptables John Dangler
2005-08-30 1:31 ` Holly Bostick
2005-08-30 2:36 ` John Dangler
2005-08-30 3:36 ` John Dangler
2005-08-30 4:54 ` John Dangler
2005-08-30 8:48 ` Hans-Werner Hilse
2005-08-30 9:43 ` Holly Bostick
2005-08-30 9:55 ` Neil Bothwick
2005-08-30 10:13 ` John Dangler
2005-08-30 1:42 ` W.Kenworthy [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-22 21:45 [gentoo-user] IPTABLES siefke_listen
2015-12-24 12:11 ` Andrew Savchenko
2015-12-24 21:41 ` siefke_listen
2015-12-29 13:09 ` lee
2009-07-16 3:32 [gentoo-user] iptables Dave
2009-07-16 8:41 ` Marco
2009-07-16 8:43 ` Marco
2009-07-16 13:42 ` Alejandro
2009-07-16 14:55 ` Nevynxxx
2007-01-18 15:58 [gentoo-user] Iptables FabrÃcio L. Ribeiro
2007-01-18 16:07 ` Daniel Pielmeier
2007-01-18 16:09 ` Nelson, David (ED, PAR&D)
2007-01-19 11:10 ` Alan McKinnon
2007-01-19 12:56 ` Pete Pardoe
2007-01-19 13:33 ` FabrÃcio L. Ribeiro
2005-08-26 3:17 [gentoo-user] iptables John Dangler
2005-08-26 4:03 ` Eric Crossman
2005-08-26 4:22 ` A. Khattri
2005-08-26 8:49 ` Fernando Meira
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=1125366124.20471.57.camel@localhost \
--to=billk@iinet.net.au \
--cc=gentoo-user@lists.gentoo.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