Re: [strongSwan] strongswan: clarification needed on rekeying failure

2012-06-29 Thread gowrishankar
Hi Martin, On Thursday 28 June 2012 01:27 PM, Martin Willi wrote: Hi, 10[IKE] received NO_PROPOSAL_CHOSEN notify, no CHILD_SA built 10[IKE] CHILD_SA rekeying failed, trying again in 24 seconds Hence, is sending notify payload (no proposal chosen) not treated as failure for rekey

Re: [strongSwan] strongswan: clarification needed on rekeying failure

2012-06-28 Thread Martin Willi
Hi, 10[IKE] received NO_PROPOSAL_CHOSEN notify, no CHILD_SA built 10[IKE] CHILD_SA rekeying failed, trying again in 24 seconds Hence, is sending notify payload (no proposal chosen) not treated as failure for rekey attempt? NO_PROPOSAL_CHOSEN usually indicates a permanent error, yes, but

[strongSwan] strongswan: clarification needed on rekeying failure

2012-06-27 Thread gowrishankar
Hi, I am looking for a clarification wrt rekeying SA in strongswan implementation. During a rekeying negotiation to a remote peer, if local node receives NO_PROPOSAL_CHOSEN in notify payload as a response to CREATE_CHILD_SA request, should n't the current IKE SA be destroyed and created once