<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Hello,<br><br>I just used the same config again in a brand new server and network this time only me as the windows client under a NAT. The server has a public IP without NAT. That scenario worked ok... but the scenario questioned in this post is still an opened issue.<br><br>Iam amazed that it is so hard to get this working between two NATtted end points... is it due to ipsec having difficulties in this manner?<br><br>Even if I get this to work is it true that since the situation would be a double NAT then in the case of two or more windows users utilizing the same NAT on their end will not be able to get packets through to the server that is also natted?<br><br>Any other way to debug this is appreciated.<br><br>Thanks<br>Gunther<br><br>> Date: Mon, 3 Jan 2011 20:36:01 -0700<br>> From: wgillespie+openswan@es2eng.com<br>> To: jprollerskate@hotmail.com<br>> CC: users@openswan.org<br>> Subject: Re: [Openswan Users] lt2p ipsec vpn does not connect. Cannot find whats wrong.<br>> <br>> On 01/03/2011 08:24 PM, JP CR wrote:<br>> > Iam guessing the NA means that iam not running a kernel with such<br>> > patches... even though I tried setting ipsec saref = no and I still<br>> > cannot establish the l2tp connection. Below is the output of auth.log<br>> <br>> Can we also see /var/log/debug so we can see the PPP debug logs?<br>> Since IPsec is working properly, we should see what's going on the L2TP <br>> side of things instead.<br>> <br> </body>
</html>