From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Brett Simpson <Simpsonb@hillsboroughcounty.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: Send local traffic to a different server.
Date: Wed, 23 Jun 2004 10:20:50 -0400 [thread overview]
Message-ID: <1088000450.24595.28.camel@localhost> (raw)
In-Reply-To: <s0d956ae.099@GroupWise>
On Wed, 2004-06-23 at 10:08, Brett Simpson wrote:
> I've tried a number of different PREROUTING and POSTROUTING rules and can't seem to make this work.
>
> I have a system with a single nic (eth0). While I'm on the system via a shell I would like to connect to 127.0.0.1:6000 and get seemlessly translated to 207.156.7.15:80.
>
> I tried the following without success:
>
> iptables -t nat -A PREROUTING -p tcp -d 127.0.0.1 -i lo --dport 6000 -j DNAT--to-destination 207.156.7.15:80
> iptables -t nat -A POSTROUTING -p tcp -d 207.156.7.15 -o eth0 --dport 80 -j SNAT --to-source 127.0.0.1
Hmmm . . . not sure, never tried it. What happens if you move your
first rule to -t nat OUTPUT instead of -t nat PREROUTING?
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2004-06-23 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 14:08 Send local traffic to a different server Brett Simpson
2004-06-23 13:33 ` Antony Stone
2004-06-23 14:33 ` Brett Simpson
2004-06-23 14:00 ` Antony Stone
2004-06-23 15:12 ` Brett Simpson
2004-06-23 14:24 ` Antony Stone
2004-06-23 16:41 ` Brett Simpson
2004-06-24 18:27 ` Brett Simpson
2004-06-23 14:20 ` John A. Sullivan III [this message]
2004-06-23 14:58 ` Antony Stone
2004-06-23 16:34 ` Brett Simpson
2004-06-23 15:39 ` B. McAninch
2004-06-23 16:53 ` Brett Simpson
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 15:26 Aldo Lagana
2004-06-24 8:46 ` Antony Stone
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=1088000450.24595.28.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=Simpsonb@hillsboroughcounty.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.