[strongSwan] reg: ikev2 notification message in response to received invalid spi message.

Hi ppl, I need some clarification in the following statement of ikev2 rfc4306 in section 1.5: If an encrypted IKE packet arrives on port 500 or 4500 with an unrecognized SPI, it could be because the receiving node has recently crashed and lost state or because of some other system malfunction

Re: [strongSwan] Kernel-netlink issue

Hi, 1. I was going through the update SA code, I figured out that the replay data for an SA is fetched separately from the other SA data, however, while adding the updated SA replay value is sent with other entries. What is the reason for this discrepancy. That's due to a limitation of the

Re: [strongSwan] strongSwan + iPhone

Hi Andreas! * Andreas Steffen andreas.stef...@strongswan.org [2009-07-13 14:40]: I think any further analysis of the strongSwan log does not give additional information. Upon the reception of the XAUTH request, the iPhone client should return its username/password. Is there any prompt on the

Re: [strongSwan] reg: ikev2 notification message in response to received invalid spi message.

At 3:04 PM +0530 7/14/09, Balaji J wrote: I need some clarification in the following statement of ikev2 rfc4306 in section 1.5: Decloaking for a moment: IKEv2 developers should strongly consider implementing from http://tools.ietf.org/html/draft-ietf-ipsecme-ikev2bis instead of from RFC 4306.