I get an error as well when I do this.  Here is my script of what I ran.  Any help is appreciated.

Script started on Wed Jun 12 23:15:18 2002
[root@natrouter root]# modprobe ipt_MASQUERADE
/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_conntrack.o: init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_conntrack.o: insmod /lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_conntrack.o failed
/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_conntrack.o: insmod ipt_MASQUERADE failed


[root@natrouter root]# iptables -F
/lib/modules/2.4.18-3/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
/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_tables.o: insmod /lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_tables.o failed
/lib/modules/2.4.18-3/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.
[root@natrouter root]#
Script done on Wed Jun 12 23:15:54 2002

-Jon "GenKiller" Gaudette


Matthew Bradford wrote:
This is the minimum that you need for a NAT.  This just turns on network address translation.  This offers no other security.  This works on my 7.2 box and it should work with 7.3 as well.  ipchains was phased out with the 2.4 kernel (7.1 release i believe)
 
 - Matt
 
modprobe ipt_MASQUERADE
iptables -F
iptables -t nat -F
iptables -t mangle -F
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
----- Original Message -----
Sent: Thursday, June 13, 2002 7:51 PM
Subject: Re: IPTables Routing Help

I was wondering if someone could help me here.  I'm despite!

I am attempting to setup a NAT router and firewall on my internal network.  It's function would be to provide an area of protection between myself and the rest of the network.  Also, I have been seriously learning Linux, and this is the next logical step.  Here's the problem, I don't have a clue what to do!  Every documentation that I find seems to contradict each other.  I am using RedHat 7.3 from downloaded ISO images.  Upon install I have installed iptables and other routing "stuff".

Upon setting it up (adding the info to my '/etc/sysconfig/network' file, etc.) One book I have states that I am to run modprobe ip_tables.  When I do so, all hell breaks loose.  Here is my error message.
[root@natrouter root]# modprobe ip_tables
/lib/modules/2.4.18-3/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
/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_tables.o: insmod /lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_tables.o failed
/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_tables.o: insmod ip_tables failed
[root@natrouter root]# 

Now, I'm lost as it is, so this just completely doesn't make sense.  This is an install from a RedHat 7.3 cd, so I'm assuming the problem is in something that I am doing.  Any help would be appreciated.

I'd also be interested in any books / documentation that explains setting up iptables for nat routing on a simple lan in "n00b" terms.  When it comes to this aspect of the "Power of Linux" ... I'm lost.  But hey, give me credit ... I want to learn.

-Jon "GenKiller" Gaudette
    
_______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list

--
-Jon "GenKiller" Gaudette
DDN Webmaster
|   http://www.digital-drip.com
CNCNZ Co-Webmaster
|   http://www.cncnz.com
APS Co-Webmaster
|   http://auburn.k12.ma.us

_______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to