From: Tom Tonk <tnbt@arcor.de>
To: netfilter@vger.kernel.org
Subject: Re: DNAT IPSec
Date: Fri, 25 Apr 2008 00:58:29 +0200 [thread overview]
Message-ID: <48111095.6070903@arcor.de> (raw)
In-Reply-To: <48110D91.7070104@arcor.de>
Tom Tonk wrote:
> problem is solved by using simply routing instead of NAT.
but anyway, would be interesting to know if the whole setup would also work
with DNAT of a service on the NAT machine to the internal box?!
prev parent reply other threads:[~2008-04-24 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 21:16 DNAT IPSec Tom Tonk
2008-04-24 22:45 ` Tom Tonk
2008-04-24 22:58 ` Tom Tonk [this message]
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=48111095.6070903@arcor.de \
--to=tnbt@arcor.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 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.