netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: amir_sarbazi <amir.sarbazi@gmail.com>
To: netdev@oss.sgi.com
Subject: iptables-problem
Date: Sat, 26 Mar 2005 22:00:02 +0430	[thread overview]
Message-ID: <43c5e5aa0503260930732eb697@mail.gmail.com> (raw)

 Hi all
  
 I have a Lan with range IP:192.168.1.0/24  that
 192.168.1.3 is my webserver.
 & have a firewall with 2 eth (eth0:192.168.1.2)
 & (eth1:217.218.68.20) .
 I want  when firewall get web request packet
 with eth1 then give it to eth0 & eth0 send
 packet to 192.168.1.3:80.
  
 I used these iptables that SNAT didn't work(Bad
 argument):
 iptables -A PREROUTING -t nat -p tcp -d
 217.218.68.20 --dport 80 -j SNAT --to
 192.168.1.2:80
 or(--to-source 192.168.1.3:80)
  
 But DNAT is working good:
 iptables -A PREROUTING -t nat -p tcp -d
 217.218.68.20 --dport 80 -j DNAT --to
 192.168.1.3 
  
 with regards.
  
 amir sarbazi

             reply	other threads:[~2005-03-26 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-26 17:30 amir_sarbazi [this message]
2005-03-26 19:13 ` iptables-problem Francois Romieu

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=43c5e5aa0503260930732eb697@mail.gmail.com \
    --to=amir.sarbazi@gmail.com \
    --cc=backslash46@yahoo.com \
    --cc=netdev@oss.sgi.com \
    /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).