R: [Openswan Users] NAT-T sucess and failure
sebastian.zdrojewski at technomind.it
Fri Apr 30 10:19:09 CEST 2004
I have tried a similar configuration within a 2.4.26 Kernel... same result when the IPsec box is nat-ted. Don't know if I have a mistake, but everything seems to be working.
> -----Messaggio originale-----
> Da: users-bounces at lists.openswan.org [mailto:users-
> bounces at lists.openswan.org] Per conto di Lewis Shobbrook
> Inviato: venerdì 30 aprile 2004 9.17
> A: users at lists.openswan.org
> Oggetto: [Openswan Users] NAT-T sucess and failure
> Hi All,
> >From an exhaustive struggle to get NAT-T working with the 2.6.5 native
> ipsec stack & openswan 2.1.x, I've found the following to be true.
> NAT-T with Win XP client works when the client only is NAT'd. When the
> freeswan box is NAT'd, the connection fails immediately after MR3,
> ISAKMP SA established... With "cannot respond to IPsec SA request
> because no connection is known". When both client and swan box are
> NAT'd we get no further than transition from state STATE_MAIN_R1 to
> state STATE_MAIN_R2.
> Can anyone dispute these results or concord?
> Users mailing list
> Users at lists.openswan.org
More information about the Users