Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Jared Cook <jared@vsahost.com>
To: netfilter@lists.netfilter.org
Subject: Using NAT to relay traffic
Date: Wed, 23 Mar 2005 17:57:41 -0600	[thread overview]
Message-ID: <42420275.7030909@vsahost.com> (raw)

I have two servers on two different networks.  I am running a service on 
box A that I am transitioning to box B.  While I wait on DNS to 
propagate, I would like to do some iptables magic to send traffic from 
box A to box B using NAT.  For instance, when pop3 email users connect 
to box A, I would like box A to send the request to box B 
transparantly.  Is this possible?  I have had success doing port 
forwarding to the local machine, but when I specify box B as the "--to", 
it doesn't work.  Any help would be greatly appreciated.

Thanks,
Jared


             reply	other threads:[~2005-03-23 23:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 23:57 Jared Cook [this message]
2005-03-24  0:37 ` Using NAT to relay traffic Grant Taylor
2005-03-24  8:44   ` Sietse van Zanen
2005-03-24 14:29     ` Jared Cook
2005-03-24 14:26   ` Jared Cook
2005-03-24 16:03     ` 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=42420275.7030909@vsahost.com \
    --to=jared@vsahost.com \
    --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