From: Bosse Klykken <bosse+netfilter@klykken.com>
To: netfilter@lists.netfilter.org
Subject: Re: no nat please
Date: Thu, 4 Nov 2004 19:53:47 +0100 [thread overview]
Message-ID: <20041104185347.GJ24014@klykken.com> (raw)
In-Reply-To: <1099591013.14542.19.camel@moola.futuresource.com>
On Thu, Nov 04, 2004 at 11:56:54AM -0600, Les Mikesell wrote:
> However there is a new standard
> for NAT traversal for IPsec and a recent Windows update adds
> it for win2k and XP. I don't know if it needs additional support
> at the NAT gateway or if you need matching versions at both
> ends, though.
Yes, IPSEC borks when one of the endpoints goes through NAT. I agree
with Les, you seem to need NAT-T, and both the server and client need
to support this, so check your VPN documentation.
I don't think that there's any need in configuring anything specific
on the NAT gateway, as long as the firewall allows UDP port 4500
(NAT-T) to flow.
.../Bosse
--
Bosse Klykken - http://www.klykken.com/~bosse
Keep staring. I might do a trick.
next prev parent reply other threads:[~2004-11-04 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 17:07 no nat please Payal Rathod
2004-11-04 17:13 ` Jason Opperisano
2004-11-04 17:56 ` Les Mikesell
2004-11-04 18:53 ` Bosse Klykken [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-04 17:13 Daniel Chemko
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=20041104185347.GJ24014@klykken.com \
--to=bosse+netfilter@klykken.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox