From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: forward/proxy/something one external IP to an other
Date: Fri, 26 Sep 2008 13:42:52 -0500 [thread overview]
Message-ID: <48DD2D2C.8030202@riverviewtech.net> (raw)
In-Reply-To: <CD6321314686A64C90A1F5870AAD3D5201566663@MAIL031.mail.lan>
On 09/26/08 11:50, Jan Agermose wrote:
> we are going to move some servers from one datacenter to an other and
> not all DNS are under our direct control so Im want to place a linux
> box in the old center to forward trafic for the old IPs to the new
> IPs - or Im hoping this is possible :) So that traffic going to the
> old IPs will still work until all DNS is updated.
Ok...
> The servers are on a NAT 1-1 network and are moved to a new 1-1 NAT
> network - if this matters?
Should not matter.
> Can someone explain if its possible and how to do it?
Yes it is possible. You will need to DNAT the traffic as it comes in to
the nat:PREROUTING chain to redirect it over to the real server as well
as SNAT the traffic as it leaves the nat:POSTROUTING chain so that the
traffic appears to the real server as if it is coming from the NATing
server. By making the traffic appear as being from the NATing server
the real server will reply back to the NATing server which can then
unNAT the traffic and reply directly back to the real client.
Or, you could run something like rinetd which will accept the
connections and then proxy them to the real server. This is extremely
easy to set up too.
Grant. . . .
next prev parent reply other threads:[~2008-09-26 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 16:50 forward/proxy/something one external IP to an other Jan Agermose
2008-09-26 18:42 ` Grant Taylor [this message]
2008-09-26 23:25 ` Brian Austin - Standard Universal
2008-09-28 18:09 ` Grant Taylor
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=48DD2D2C.8030202@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.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