Finally I made it work.<br><br>A had a good look at the book Building and Integrating VPN with Openswan, which cleared things for me.<br><br>My mistakes at the time were:<br>1) I was ping'ing the external IP of the other gateway to test a gateway-to-gateway connection. If you do that the packet will not be encripted.<br>
2) I was not setting rightsourceip, so when I ping'ed the internal IP of the other gateway I had no response.<br><br>After that I was having other problems.<br>On my server that is behind nat I had to do a port foward (DNAT) of the gateway to the IPSec server machine.<br>
The roadwarrior side of ipsec was not recognizing the ID of the server. That's because the server send it's id as his internal IP address, and the client was expeting the external one.<br>To fix that I had to set the rightid=<Internal IP of IPSec Server> on roadwarrior's ipsec.conf.<br>
<br>Now everthing is working fine. Thank's for your help, and thank you to the developers for the great work.<br><br><div class="gmail_quote">On Wed, Mar 23, 2011 at 6:08 PM, David McCullough <span dir="ltr"><<a href="mailto:david_mccullough@mcafee.com" target="_blank">david_mccullough@mcafee.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Jivin Diogo V. kersting lays it down ...<br></blockquote><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Perhaps you can describe your problem with NAT-T and 2.6.37 ?<br>
<br>
Cheers,<br>
Davidm<br>
<font color="#888888"><br></font></blockquote></div><br>