I had added those as well ... with one command for each interface ... still no go .. the packets are still dropped as the forward is attempted *scratches head* I added two commands ... one for each -i eth0 and -i eth1 .. still no go Randy ----- Original Message ----- From: "Jima" <jima at beer.tclug.org> To: "Randy Clarksean" <rclark at lakesplus.com>; "TCLUG Mailing List" <tclug-list at mn-linux.org> Sent: Thursday, June 17, 2004 1:21 PM Subject: Re: [TCLUG] redirect with iptables command > On Thu, 17 Jun 2004, Randy Clarksean wrote: > > That did take care of the error for the iptables command .. but it still > > does not make it through the firewall. The packets still die ... nothing > > makes it to the internal machine. > > How's your FORWARD table looking? You need a rule open like: > > $IPT -A FORWARD -i eth1 -i eth0 -p tcp -d 192.168.1.99 --dport 22 -j ACCEPT > > that says that's it's okay to forward packets from outside to > 192.168.1.99:22 (after the destination got rewrote). > > Jima > _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota Help beta test TCLUG's potential new home: http://plone.mn-linux.org Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list