error: ip_tables.o init_module:Device or resource busy

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.
******************************************************

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...

Presumably that's a stock RH kernel. For starters, 2.4.22 is completely stable and offers a noticeable improvement in throughput. You might want to custom compile and install it yourself.

---------
Quality Management - A Commitment to Excellence

Dear David,

Thanks for the advice.
Seeing as I have never manually done a kernel install, I have just taken the following steps:-
-upgraded to iptables 1.2.8 from tar.gz
-installed kernel 2.4.22-1.2115.nptl using "no-brain" rpm commands. Those purists amongst the list readers will be happy to note this has not got me anywhere:-
*******************************************************************
iptables -L /lib/modules/2.4.22-1.2115.nptl/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.22-1.2115.nptl/kernel/net/ipv4/netfilter/ip_tables.o:
insmod /lib/modules/2.4.22-1.2115.nptl/kernel/net/ipv4/netfilter/ip_tables.o failed /lib/modules/2.4.22-1.2115.nptl/kernel/net/ipv4/netfilter/ip_tables.o:
insmod ip_tables failed
iptables v1.2.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
*********************************************************************

At this stage, am I going to have to manually configure the kernel ?? I guess so, but seeing as I do not know what I am doing, I'd appreciate any input from somebody who knows what they are doing.

steve

Dear All,

Okay, I have managed to fix the problem in a "no-brain" way. The problem had probably) occurred because I installed the new version of iptab(les from the source package, and I (stupidly) had it installed at the same time as the old iptables package .
I got rid of all the iptables installs (and ipchains and auto-installed firewalls) I could find on my disk, and reinstalled iptables 1.2.8-8 from an rpm.
Now everything seems to work !
Phew, I am saved from kernel compiling once again...
Thanks for everybodies' input

steve

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.

	Alistair Tonner
	nerdnet.ca
	Senior Systems Analyst - RSS
	
     Any sufficiently advanced technology will have the appearance of magic.
	Lets get magical!

hi steve & alistair,

you might also want to see this ...

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=103177

cheers

charles