netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Klettke <thomas@klettke.us>
To: "Diego R. Rodriguez Herlein" <diegorh@infovia.com.ar>
Cc: Leszek Zur <lzur@record.com.pl>, netfilter@lists.netfilter.org
Subject: Re: POSTROUTING & DNAT
Date: Wed, 10 Sep 2003 06:59:21 -0500	[thread overview]
Message-ID: <1063195160.4399.0.camel@klettke.us> (raw)
In-Reply-To: <1b7301c3774d$2d14a260$8201a8c0@lw1dqwin>

Is NAT support compiled into the kernel?


On Tue, 2003-09-09 at 22:39, Diego R. Rodriguez Herlein wrote:
> Sorry those are my rules (DMZ)
> 
> HTTP
> #
> iptables -t nat -A PREROUTING -p tcp -d $IP_REAL --dport 80 -j DNAT \
> --to-destination $IP_DMZ
> iptables -t nat -A POSTROUTING -p tcp -d $IP_DMZ --dport 80 -j SNAT \
> --to-source $IP_LAN
> iptables -t nat -A OUTPUT -p tcp -d $IP_REAL --dport 80 -j DNAT \
> --to-destination $IP_DMZ
> #
> #
> #
> work great with rh 7.1 kernel 2.4.17
> 
> 
> ----- Original Message ----- 
> From: "Leszek Zur" <lzur@record.com.pl>
> To: <netfilter@lists.netfilter.org>
> Sent: Thursday, May 22, 2003 10:01 AM
> Subject: POSTROUTING & DNAT
> 
> 
> > Hello
> > 
> > iptables -t nat -A OUTPUT -d 1.1.1.1 -j DNAT --to-destination 2.2.2.2
> > iptables: Invalid argument
> > 
> > Can anyone help me understand what is happening?
> > 
> > iptables v1.2.8
> > kernel 2.4.20
> > 
> > thnx
> > 
> > Leszek
> > 
> > 
> > 
> 


  reply	other threads:[~2003-09-10 11:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 13:01 POSTROUTING & DNAT Leszek Zur
2003-09-10  3:19 ` Diego R. Rodriguez Herlein
2003-09-10  3:39 ` Diego R. Rodriguez Herlein
2003-09-10 11:59   ` Thomas Klettke [this message]
2003-09-10 21:55     ` Diego R. Rodriguez Herlein
2003-09-11  0:29       ` Thomas Klettke
2003-09-11 21:35         ` Diego R. Rodriguez Herlein

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=1063195160.4399.0.camel@klettke.us \
    --to=thomas@klettke.us \
    --cc=diegorh@infovia.com.ar \
    --cc=lzur@record.com.pl \
    --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;
as well as URLs for NNTP newsgroup(s).