From: Simon Tennant <simon@imaginator.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org
Subject: Re: DNAT issue (with added network diagram)
Date: Mon, 03 May 2010 16:21:24 +0200 [thread overview]
Message-ID: <4BDEDBE4.3020803@imaginator.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1005031601340.29150@obet.zrqbmnf.qr>
On 03/05/2010 16:01, Jan Engelhardt wrote:
>> 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?\
>>
> Since they have all public addresses, no NAT is needed.
>
Just to clarify: both services run on one host. The second host (maar)
doesn't host any services and shouldn't. It's role in this is just
forwarding maar:443 -> cave:5222. Ordinarily I'd just have a listener
for xmpp on cave:443 but that's taken by apache. Hence this packet
wangling.
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
next prev parent reply other threads:[~2010-05-03 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 13:23 DNAT issue (with added network diagram) Simon Tennant
2010-05-03 14:01 ` Jan Engelhardt
2010-05-03 14:21 ` Simon Tennant [this message]
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=4BDEDBE4.3020803@imaginator.com \
--to=simon@imaginator.com \
--cc=jengelh@medozas.de \
--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).