From: Alistair Tonner <Alistair@nerdnet.ca>
To: Steve <info@fabsurplus.com>, netfilter@lists.netfilter.org
Subject: Re: error: ip_tables.o init_module:Device or resource busy
Date: Mon, 10 Nov 2003 18:42:39 -0500 [thread overview]
Message-ID: <200311101842.39637.Alistair@nerdnet.ca> (raw)
In-Reply-To: <3FAFCFEC.8010700@fabsurplus.com>
On November 10, 2003 12:50 pm, Steve wrote:
> I'd like to preface this mail by saying that if a little knowledge is a
> dangerous thing, then I am very dangerous....
>
> I have recently installed redhat 9.0 over the top of RH V7.3 and then I
> upgraded to iptables 1.2.7a with a 2.4.20-18.9 kernel using apt-get.
> When I try to do anything with iptables, I get the following error:-
>
> *************************************************************
> e.g. iptables -F
> /lib/modules/2.4.20-18.9/kernel/net/ipv4/netfilter/ip_tables.o:
> init_module: Device or resource busy
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters.
> You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.20-18.9/kernel/net/ipv4/netfilter/ip_tables.o: insmod
> /lib/modules/2.4.20-18.9/kernel/net/ipv4/netfilter/ip_tables.o failed
> /lib/modules/2.4.20-18.9/kernel/net/ipv4/netfilter/ip_tables.o: insmod
> ip_tables failed
> iptables v1.2.7a: can't initialize iptables table `filter': iptables
> who? (do you need to insmod?)
> Perhaps iptables or your kernel needs to be upgraded.
> ******************************************************
I note that Stephen has fixed the problem, but for the record, this error is
generated when ipchains is loaded either as a module or in the kernel and one
attempts to use iptables.
>
> Obviously (?), there is something wrong with either the kernel or
> iptables as I have installed it .
> I need to get iptables working yesterday.
> Can anyone tell me a no-brainer way to achieve this ?
> Does my version of kernel work with this version of iptables ?
> Do I have to go back to an earlier version ?
> Whats the best way to get out of this mess ?
> I remember for my dos days we used to do "format c:" in this kind of
> situation.
>
> Thanks a lot,
>
> Steve
>
> Update: I installed iptables 1.2.8 from tar.gz: same problem.
> Hence, either it's a hardware config. problem (?), or kernel is setup
> wrong. I am now tring to recompile the kernel using v 2.4.22.
> Any help would be much appreciated as I have little idea how to
> recompile a kernel and all I need is iptables working, I'd rather avoid
> all this kernel stuff...
--
Alistair Tonner
nerdnet.ca
Senior Systems Analyst - RSS
Any sufficiently advanced technology will have the appearance of magic.
Lets get magical!
next prev parent reply other threads:[~2003-11-10 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 17:50 error: ip_tables.o init_module:Device or resource busy Steve
2003-11-10 19:04 ` David C. Hart
2003-11-10 20:05 ` Stephen CS Howe
2003-11-10 20:50 ` Stephen CS Howe
2003-11-10 23:42 ` Alistair Tonner [this message]
2003-11-11 7:44 ` christopher cuse
-- strict thread matches above, loose matches on Subject: below --
2003-11-10 15:08 Steve
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=200311101842.39637.Alistair@nerdnet.ca \
--to=alistair@nerdnet.ca \
--cc=info@fabsurplus.com \
--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