I got this iptables problem after executing the ff iptables script in
kernel 2.4.18-17.7.x

--[ snip ]--
iptables -t nat -A PREROUTING -i eth1-p TCP --dport 80 -s 0.0.0.0/0 -j
DNAT --to 192.168.0.204:80
iptables -A INPUT - p TCP -d 192.168.0.204 --dport 80 -s 0.0.0.0/0 -j
ACCEPT
iptables -A FORWARD -p TCP -d 192.168.0.204 --dport -s 0.0.0./0 -j
ACCEPT
--[ snip ]--

then I check the iptables using iptables -L, and I get the following
error:

[root@FWall sysconfig]# iptables -L
/lib/modules/2.4.18-17.7.x/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.18-17.7.x/kernel/net/ipv4/netfilter/ip_tables.o: insmod
/lib/modules/2.4.18-17.7.x/kernel/net/ipv4/netfilter/ip_tables.o failed
/lib/modules/2.4.18-17.7.x/kernel/net/ipv4/netfilter/ip_tables.o: insmod
ip_tables failed
iptables v1.2.5: can't initialize iptables table `filter': iptables who?
(do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.


Thanks,
Andy



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to