From: "John Dangler" <jdangler@atlantic.net>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] iptables
Date: Tue, 30 Aug 2005 00:54:47 -0400 [thread overview]
Message-ID: <002201c5ad1f$04a9de80$0501a8c0@croatus> (raw)
In-Reply-To: <001a01c5ad14$1837fa00$0501a8c0@croatus>
yep. it's a bug. As soon as I remove iptables from the kernel config,
ipw2100,ieee80211_crypt_tkip, ieee80211_crypt_ccmp, ieee80211_crypt_wep,
ieee80211 all show up fine in lsmod. no dmesg errors, and eth1 (wireless)
shows up fine. Off to bugz to log this.
John D
-----Original Message-----
From: John Dangler [mailto:jdangler@atlantic.net]
Sent: Monday, August 29, 2005 11:36 PM
To: gentoo-user@lists.gentoo.org
Subject: RE: [gentoo-user] iptables
ok. I got a clean kernel and removed iptables and firestarter. I then went
into the kernel config and _only_ turned on iptable support as a module, and
ran modules-update. all looks ok. Rebooting the kernel, however, I get
this in dmesg -
ipw2100: disagrees about version of symbol per_cpu__softnet_data
ipw2100: no version for "ieee80211_get_crypto_ops" found: kernel tainted.
(a whole lot of these messages listing what appears to be every symbol in
the ipw2100 module)...
then -
ieee80211: disagrees about version of symbol per_cpu__softnet_data
ieee80211: Unknown symbol per_cpu__softnet_data.
(a whole lot of these messages listing what appears to be every symbol in
the ieee80211 module)...
then -
ieee80211_crypt_wep: disagrees about version of symbol ___pskb_trim
ieee80211_crypt_wep: Unknown symbol ___pskb_trim.
(a whole lot of these messages listing what appears to be every symbol in
the ieee80211_crypt_wep module)...
It appears that the version of ipw2100 and/or ieee80211 in portage (stable)
clashes with the version of iptables in portage (stable).
So, either I can have wireless or security...
John D
-----Original Message-----
From: John Dangler [mailto:jdangler@atlantic.net]
Sent: Monday, August 29, 2005 10:36 PM
To: gentoo-user@lists.gentoo.org
Subject: RE: [gentoo-user] iptables
Holly~
The Firestarter kernel requirements doc says -
*Device drivers
*Networking support [y]
*Networking support
*Networking options
*Network packet filtering [y]
*Network packet filtering
IP: Netfilter Configuration
(*)
"We recommend you enable _everything_ except ipchains support and ipfwadm
support as modules under this menu"
In case I did something out to bork this myself, I'm going to unmerge
firestarter and iptables, rebuild the kernel into the state it was before
this started (genkernel --kernel-config=my.old.config all), emerge iptables
(instead of letting firestarter emerge do it), make sure that iptables loads
up ok, then emerge firestarter and configure it. That way, I can be sure
that it's not me just getting in a hurry to install a package...
John Dangler
GenoFit
800-505-4078 (Corporate)
386-767-3730 (Direct)
866-273-0408 (Fax)
www.genofit.com
jdangler@genofit.com
-----Original Message-----
From: Holly Bostick [mailto:motub@planet.nl]
Sent: Monday, August 29, 2005 9:32 PM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] iptables
John Dangler schreef:
> 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)
Oh, John, to hell with "the doc you found" (which look to be from the
Wiki). No offense to the wiki (or to you), but you're really
overcomplicating this. You're probably better off with the Firestarter
docs found here
http://www.fs-security.com/docs/kernel.php
which are complete, and clear, and designed to work with the Firestarter
front end.... you know, "official docs"...? :)
Holly
--
gentoo-user@gentoo.org mailing list
--
gentoo-user@gentoo.org mailing list
--
gentoo-user@gentoo.org mailing list
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-30 4:59 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 [this message]
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
-- 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='002201c5ad1f$04a9de80$0501a8c0@croatus' \
--to=jdangler@atlantic.net \
--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