From mboxrd@z Thu Jan 1 00:00:00 1970 From: Herman Subject: Re: Invalid friggen argument Date: Sun, 12 Oct 2003 12:18:25 -0600 Sender: netfilter-admin@lists.netfilter.org Message-ID: <200310121218.25934.Herman@AerospaceSoftware.com> References: Reply-To: Herman@AerospaceSoftware.com Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: markee@bandwidthco.com, netfilter@lists.netfilter.org On Sunday 12 October 2003 11:44 am, Mark E. Donaldson wrote: I don't think you have a versioning problem. Some of the more recent releases of netfilter are more sensitive about arguments and argument ordering I have found. Are you able to slip in a destination address into that rule: iptables -t nat -A PREROUTING -i eth1 -p tcp -d xxx.xxx.xxx.xxx --dport 6390 \ -j DNAT --to 192.168.10.245 It may be looking for a dest address. I have tried that before and here goes: iptables -t nat -A PREROUTING -i eth1 -p tcp -d 192.168.10.100 --dport 6390 -j DNAT --to 192.168.10.245 iptables: Invalid argument No luck. Cheers, -- Herman