From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: netfilter@lists.netfilter.org
Subject: Re: "distributed router" question
Date: Sat, 24 Feb 2007 19:58:46 -0600 [thread overview]
Message-ID: <erqqgn$omf$1@sea.gmane.org> (raw)
In-Reply-To: <47965.8371689313$1172352756@news.gmane.org>
Alec Matusis wrote:
> Hi Silvio,
>
> Thanks for your response.
>
> I still do not understand why SNATting in B to public IP of box A would not
> work?
> By this I mean the following:
>
> 1) Client sends packet to box A ( src: 9.10.11.12 dst: 1.2.3.4 )
> 2) Box A does DNAT (PREROUTING) to box B ( src: 9.10.11.12 dst: 10.0.0.2 )
>
> Box B receives the packet and replies directly to the client:
> 1) Box B does SNAT (POSTROUTING) using box A WAN as source (src: 1.2.3.4
> dst: 9.10.11.12)
>
> There are two reasons why I'd like to implement it this way:
>
> a) Reduce the load on box A so that the packets from B go directly to the
> client 9.10.11.12, bypassing A.
> b) The server on box B must log the IPs of all clients (i.e. log the
> original client IP 9.10.11.12)
>
> Thank you,
>
> Alec Matusis
You can make that work for UDP, but for TCP box A will see only half-open
connections (it will never see the SYN/ACK) and reject the payload packets
as invalid.
--
Bob Nichols Yes, "NOSPAM" is really part of my email address.
next prev parent reply other threads:[~2007-02-25 1:58 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 [this message]
2007-02-25 7:30 ` Alec Matusis
2007-02-27 16:51 ` Robert Nichols
[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='erqqgn$omf$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.