From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David Busby" Subject: Re: SNAT "invalid argument" Date: Mon, 4 Aug 2003 12:08:38 -0700 Sender: netfilter-admin@lists.netfilter.org Message-ID: <06a001c35abb$cfcf0120$1100000a@busbydev> References: <20030804185601.GA8546@free.transpect.com> Reply-To: "David Busby" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: 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: Whit Blauvelt , netfilter@lists.netfilter.org In this doc http://www.netfilter.org/documentation/HOWTO//NAT-HOWTO-6.html#ss6.1 it says use --to-source, not --to /B ----- Original Message ----- From: "Whit Blauvelt" To: Sent: Monday, August 04, 2003 11:56 Subject: SNAT "invalid argument" > Hi, > > I've been using SNAT for some time on several systems. However on a system I > just built I get the following response: > > # iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to 1.2.3.4 > iptables: Invalid argument > > That's with 1.2.3.4 replaced by a real IP (or not). > > This is driving me up the wall since "Full NAT" support is compiled into > the 2.4.21 kernel. The iptables version is 1.2.8. The only thing different > in the kernel options from what I've used before is that I also included > "NAT of local connections" - haven't tried to use that yet though. > > iptables is otherwise working fine. -j MASQUERADE (also compiled in) also > gives me an "Invalid argument" - so it does look like something's wrong in > the NAT section, but damned if I know what. > > Whit >