Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ranjeet Shetye <ranjeet.shetye2@zultys.com>
To: netfilter@lists.netfilter.org
Subject: Re: Problems after recompiling iptables 1.2.7 ..
Date: 20 Jan 2003 09:05:40 +0100	[thread overview]
Message-ID: <1043049940.4920.4.camel@knoppix> (raw)
In-Reply-To: <200301201432.52665.fabio@gekolab.it>

On Mon, 2003-01-20 at 14:32, Fabio Corneti wrote:
> On Monday 20 January 2003 08:59, Raymond Leach wrote:
> > Hi
> >
> > I have a problem with NAT after recompiling iptables and my kernel.
> >
> > This line gives an 'invalid argument' error:
> > iptables -t nat -A PREROUTING -i eth0 -s 192.168.0.0/24 -j SNAT
> > --to-source 196.4.160.2
> >
> > Is there something wrong with the above line, or is there something
> > wrong with my kernel or iptables?
> >
> > kernel version = 2.4.20 - 'Full Nat' is enabled
> > patch-o-matic 'time' patch applied
> > iptables version = 1.2.7
> >
> > There were no errors during compile. Although, after rebooting the
> > machine complains about a missing map file.
> >
> > Regards
> >
> > Ray
> 
> Shouldn't be specified an output interface/address with the -o option? 
> Moreover, I think that if you want to do source nat, you should do it in the 
> POSTROUTING chain. Try this (the existence of another network card eth1 is 
> presumed):
> 
> iptables -t nat -A POSTROUTING -i eth0 -o eth1 -s 192.168.0.0/24 -j SNAT
> --to-source 196.4.160.2
> 
> -- 
> Fabio Corneti
> fabio@gekolab.it
> 

You are right.

SNAT MUST be done in the POSTROUTING chain.

Also, it MUST take an outgoing interface.

The incoming interface MAY BE specified if you have specific needs.

Ranjeet.




  reply	other threads:[~2003-01-20  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20  7:59 Problems after recompiling iptables 1.2.7 Raymond Leach
2003-01-20 13:32 ` Fabio Corneti
2003-01-20  8:05   ` Ranjeet Shetye [this message]
2003-01-20 18:17     ` Martin Josefsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1043049940.4920.4.camel@knoppix \
    --to=ranjeet.shetye2@zultys.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox