All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alec Matusis" <alecm@chatango.com>
To: lartc@vger.kernel.org
Subject: [LARTC] routing TCP to another box preserving ORIGINAL client IPs
Date: Thu, 08 Mar 2007 04:07:13 +0000	[thread overview]
Message-ID: <004301c76137$40fdaa10$c2f8fe30$@com> (raw)

My TCP clients connect to box A. I need to forward those connections to a
server on box B, such that the original client IPs are visible to the server
on B.

Each box has two Ethernet ports. One port on each box is connected to WAN,
and they are cross-connected in a LAN via remaining ports:

        -------------------           -------------------
WAN -- |eth0   Box A   eth1|---LAN---|eth1   Box B   eth0| -- WAN
        -------------------           -------------------


Is there a way to do this with iproute2 and iptables tools ONLY? Can you
provide an example? Nothing in Google after more than a week of searching.
An additional requirement is to reduce the load on box A as much as possible
(I guess the server on B would still have to reply to the client via A, not
using B's own WAN interface however..)


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-03-08  4:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  4:07 Alec Matusis [this message]
2007-03-08  4:23 ` [LARTC] routing TCP to another box preserving ORIGINAL client IPs Martin A. Brown
2007-03-08  4:46 ` Alec Matusis
2007-03-09  0:05 ` Alec Matusis
2007-03-09  0:48 ` ArcosCom Linux User
2007-03-09  3:13 ` Alec Matusis
2007-03-09  4:31 ` Rangi Biddle
2007-03-09  4:38 ` Alec Matusis
2007-03-09  4:39 ` Martin A. Brown
2007-03-09  8:16 ` Alec Matusis
2007-03-09 15:43 ` Martin A. Brown

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='004301c76137$40fdaa10$c2f8fe30$@com' \
    --to=alecm@chatango.com \
    --cc=lartc@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 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.