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
Hi,
I am testing IKEv2 implementation for invalid but critical payload type.
strongswan seems to be sending notification payload of message type
UNSUPPORTED_CRITICAL_PAYLOAD as expected. But, notification data is
corrupted where as it should be a one-octet payload type as per
Section 2.5 of RFC
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 is not defined according to IANA.
Andreas
On 07/01/2012 01:39 PM, gowrishankar wrote:
Hi,
I am testing IKEv2
