From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Source NAT
Date: Sat, 3 Sep 2005 15:29:54 -0500 [thread overview]
Message-ID: <200509031529.54803.rob0@gmx.co.uk> (raw)
In-Reply-To: <WorldClient-F200509031428.AA28260029@acerlandslp.com.mx>
On Saturday 2005-September-03 14:28, ISC Jorge Ceron Galvan wrote:
> > > I currently have a situation that I am hoping iptables can
> > > resolve. The issue is that I need to NAT the source address based
> > > on the destination address. Is that possible with IPTables ?
> >
> > Trivial.
> >
> > > if dst = 1.1.1.1 src = 10.1.1.1
> >
> > iptables -vt nat -A POSTROUTING -d 1.1.1.1 -j SNAT -to 10.1.1.1
>
> why -vt?
>
> this rule confused me, I'm a begginer;
All the more reason to RTFM, as previously suggested. Hint: the -v
option to iptables does the same thing as does the -v option to most
other command line programs.
> what about
>
> iptables -t nat -A POSTROUTING -s 10.1.1.1/24 -j SNAT --to 1.1.1.1
This is not what the OP said was wanted. That is SNAT based on the
source address, not the destination.
> iptables -t nat -A POSTROUTING -o eth0 -s 10.1.1.1/24 -j SNAT --to
> 1.1.1.1
Same thing, with the additional specification of output interface. You
can, of course, specify more matching options to limit the packets
selected by the rule. It *is* common to limit SNAT based upon source
address too.
> > > Can anyone give me any advice on completing that?
> >
> > "man iptables"
> >
> > Order matters. If you have a catchall SNAT rule before the specific
> > destination ones, the catchall is the one used.
> >
> > NAT != routing. If your SNAT'ed IP addresses need to go out
> > different interfaces, this won't work. See the LARTC HOWTO.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2005-09-03 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 11:18 Source NAT Jimmy
2005-08-31 11:31 ` Stéphane BENOLIEL
2005-08-31 11:33 ` Stéphane BENOLIEL
2005-08-31 11:37 ` /dev/rob0
2005-09-03 19:28 ` ISC Jorge Ceron Galvan
2005-09-03 20:29 ` /dev/rob0 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 18:49 Michael Forrest
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=200509031529.54803.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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