[EMAIL PROTECTED] root]# iptables -t nat -A PREROUTING -p tcp -s x.x.x.x --dport 25 -j DNAT --to 192.168.0.5:25 /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 `nat': iptables who? (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.
----- Original Message ----- From: "MonMotha" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, September 01, 2002 10:13 PM Subject: Re: [luau] Port Forwarding 2.4 kernel (RH 7.3) > MonMotha wrote: > > Unfortunately, 2.4 can't use ipmasqadm, and ipchains can't do port > > forwards on it's own, so you'll have to use iptables for this. Of > > course this means converting whatever rulesets you might have (which may > > be a problem). > > > > However, iptables is pretty flexible. To forward a port: > > iptables -t nat -A PREROUTING -p tcp -s $ExtHostIP --dport 25 --to > > 192.168.0.5:25 > > > > Make sure you allow it on the forward table. > > > > --MonMotha > > D'oh! Forgot the -j DNAT: > > > iptables -t nat -A PREROUTING -p tcp -s $ExtHostIP --dport 25 -j DNAT > --to 192.168.0.5:25 > > --MonMotha > > _______________________________________________ > LUAU mailing list > [EMAIL PROTECTED] > http://videl.ics.hawaii.edu/mailman/listinfo/luau >
