netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Tennant <simon@imaginator.com>
To: netfilter@vger.kernel.org
Subject: DNAT issue (with added network diagram)
Date: Mon, 03 May 2010 15:23:38 +0200	[thread overview]
Message-ID: <4BDECE5A.4010808@imaginator.com> (raw)

Problem:

Two different applications that need to be accessible on port 443 on one 
host with 1 ip address.  Apache already runs on the destination machine 
and uses port 443.

Partial solution:

1. Change DNS to tell the client to connect to another host, and.
2. use another host that is not running anything on port 443 to receive 
and forward the connctions using a "-j DNAT --to-destination" rule.

But:

What happens when a client on the destination also needs to connect and 
looks up the service in DNS?  It connects out and is DNAT'ed back to itself.

A quick diagram:

http://docs.google.com/drawings/pub?id=1dxCOw8wbAhyuz7z1-ukJfmKOHcymsqN6YTRCjrTh_MY&w=1440&h=1080

My question is what DNAT or SNAT rules do we need to add to cave or to 
maar so that remote *and local (originating from cave)* clients can make 
xmpp connecitons on 443 and end up on cave:5222?

S.

-- 
Simon Tennant

+44 20 7043 6756 (UK - office)
+49 17 8545 0880 (Germany - mobile)
+49 89 4209 55854 (Germany - office)
skype: simontennant
xmpp: simon@buddycloud.com


             reply	other threads:[~2010-05-03 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 13:23 Simon Tennant [this message]
2010-05-03 14:01 ` DNAT issue (with added network diagram) Jan Engelhardt
2010-05-03 14:21   ` Simon Tennant
2010-05-03 16:24     ` Steve Fink
2010-05-03 16:52       ` Simon Tennant

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=4BDECE5A.4010808@imaginator.com \
    --to=simon@imaginator.com \
    --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;
as well as URLs for NNTP newsgroup(s).