All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: netfilter@lists.netfilter.org
Subject: Re: "distributed router" question
Date: Tue, 27 Feb 2007 10:51:39 -0600	[thread overview]
Message-ID: <es1nis$15m$1@sea.gmane.org> (raw)
In-Reply-To: <539.336764677678$1172388665@news.gmane.org>

Alec Matusis wrote:
> Thanks Robert.
> 
> My requirement is to have a transparent proxy in some sense: the TCP packets
> should be proxied by box A to a server on box B, and back from B to the
> client (via A I guess). The server on box B should see the original IP
> address of the client. When I do SNAT on A, the original IP becomes
> invisible for box B.

You just need to ensure that packets from B to the client get routed via
box A.  That is a routing issue, not a netfilter problem.  Depending on
what other traffic is going to/from box B, the solution could be as simple
as making box A the gateway for the default route out of box B.  If B
is handling other traffic that does not go through A, then you'll
probably need to use the advanced routing features of iproute2 to
selectively route the packets.  There's a rather extensive "Linux Advanced
Routing & Traffic Control HOWTO" available from http://lartc.org .

-- 
Bob Nichols         Yes, "NOSPAM" is really part of my email address.



  reply	other threads:[~2007-02-27 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200702241418.22551.silvio@pizzaroot.com.br>
2007-02-24 21:31 ` "distributed router" question Alec Matusis
2007-02-25  1:58   ` Robert Nichols
2007-02-25  7:30     ` Alec Matusis
2007-02-27 16:51       ` Robert Nichols [this message]
     [not found] <20070224075255.F2B1928985@supreme.pizzaroot.com.br>
2007-02-24 16:26 ` Silvio Fonseca
2007-02-24  6:50 Alec Matusis

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='es1nis$15m$1@sea.gmane.org' \
    --to=rnicholsnospam@comcast.net \
    --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.