[Openswan Users] subnet-to-subnet problem
amin_o_city at yahoo.com
Tue Oct 13 12:38:36 EDT 2009
Thanks for your fast reply.
The PSK key of both sides is "123" :) , and it works fine with host to host configuration.
Also, we are restricted to use linux 126.96.36.199 , and i think cross-compiling openswan 2.6.23 on this kernel takes along time.
Could you please explain me , where the problem is , or if there is any patches for openswan-2.6.19 to solve this problem.
Thanks in advance.
----- Original Message ----
From: Paul Wouters <paul at xelerance.com>
To: farajian amin <amin_o_city at yahoo.com>
Cc: users at openswan.org
Sent: Tue, October 13, 2009 7:26:31 PM
Subject: Re: [Openswan Users] subnet-to-subnet problem
On Tue, 13 Oct 2009, farajian amin wrote:
> We have 2 embbeded boards with sparc 200Mhz processors running linux 188.8.131.52. We have added openswan 2.6.19 with KLIPS support on it. They work fine with together when the ipsec.config contains only host to host configurations.
> The problem is started when we want to have a subnet to subnet configuration, at it shows itself as a series of commands as follows.
> In the initiator board :
> ----- "net_to_net" #2: message ignored because it contains an unexpected payload type ISAKMP_NEXT_HASH)
> ----- "net_to_net" #2: sending encrypted notification INVALID_PAYLOAD_TYPE to 192.168.1.87:500
This was fixed in openswan 2.6.23. (or you made a typo in the PSK)
More information about the Users