Hi Zhiheng,
I am also seeing this UDP_ENCAP error in 5.0.1rc1 on my Red Hat Enterprise
Linux 5.6 machine.
I did not see it in the 5.0.0 release, so looks like this error is new
in 5.0.1 and is happening not only on the FreeBSD:
Sep 27 11:44:53 sit-iwf charon: 00[DMN] Starting IKE charon
btw I am using StrongSwan 5.0.0
-Neeraj
From: kaj...@live.in
To: e...@cendatsys.com; users@lists.strongswan.org
Date: Fri, 28 Sep 2012 16:58:53 +0530
Subject: Re: [strongSwan] Cannot do IKEv1/PSK Main Mode in Cisco ASA 5510
# ipsec.conf
config setup
charondebug=dmn 1
conn %default
Hi Andreas,
I could not follow up on your reply by that time.
On Sunday 01 July 2012 06:43 PM, Andreas Steffen wrote:
What do you mean by corrupted? To my unexperienced eyes the log shows
that indeed a one-octet notification payload is sent containing the
received and rejected value 0x2D which
Hi Gowri,
Here, this payload is of 9 bytes as payload length also mentions
correctly. But, my doubt is on notification data which is 2D.
It is always 2D even if I set notification data on sending node (say 01).
This value has nothing to do with the notification data, but with the
payload type
Hi Tobias,
On Saturday 29 September 2012 02:04 AM, Tobias Brunner wrote:
Hi Gowri,
Here, this payload is of 9 bytes as payload length also mentions
correctly. But, my doubt is on notification data which is 2D.
It is always 2D even if I set notification data on sending node (say 01).
This
