From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Send local traffic to a different server.
Date: Wed, 23 Jun 2004 15:58:00 +0100 [thread overview]
Message-ID: <200406231558.00325.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <s0d956ae.099@GroupWise>
On Wednesday 23 June 2004 3:08 pm, 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 might as well just check something rather obvious:
Can you access 207.156.7.15:80 from the machine we are talking about?
ie: assuming we get the NAT to work the way you want, do the packets get to
the remote server and the replies back again okay?
Antony.
--
If you can't find an Open Source solution for it, then it isn't a real
problem.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-06-23 14:58 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
2004-06-23 14:58 ` Antony Stone [this message]
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=200406231558.00325.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.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