Re: [strongSwan] IKE_SA_INIT response with notification data missing

2018-04-16 Thread Tobias Brunner
> Is there any reason why UDP checksum in the packet shows as wrong in the > wireshark? Possibly hardware checksum offloading [1]. Regards, Tobias [1] https://wiki.wireshark.org/CaptureSetup/Offloading

Re: [strongSwan] IKE_SA_INIT response with notification data missing

2018-04-16 Thread Balaji Thoguluva Bapulal
<balaji.thoguluva.bapu...@oracle.com>; users@lists.strongswan.org Subject: Re: [strongSwan] IKE_SA_INIT response with notification data missing Hi Balaji, RFC 4739 "Multiple Authenticaton Exchanges in IKEv2" https://tools.ietf.org/html/rfc4739#section-3.1 defines the format of the MULTI

Re: [strongSwan] IKE_SA_INIT response with notification data missing

2018-04-16 Thread Andreas Steffen
Hi Balaji, RFC 4739 "Multiple Authenticaton Exchanges in IKEv2" https://tools.ietf.org/html/rfc4739#section-3.1 defines the format of the MULTIPLE_AUTH_SUPPORT Notify Payload as 3.1. MULTIPLE_AUTH_SUPPORTED Notify Payload The MULTIPLE_AUTH_SUPPORTED notification is included in the

Re: [strongSwan] IKE_SA_INIT response with notification data missing

2018-04-15 Thread Balaji Thoguluva Bapulal
Also the UDP checksum in the IKE_SA_INIT response shows incorrect in wireshark. From: Balaji Thoguluva Bapulal Sent: Saturday, April 14, 2018 10:42 PM To: users@lists.strongswan.org Subject: IKE_SA_INIT response with notification data missing Dear users, I am trying to establish a