Hi Andreas, Thanks for your prompt reply. I have one more clarification from your side.
1) How Strongswan is classifying "delete payload coming for deleting Child SA's, when the peer stops IPSec service and delete payload coming for deleting old Child SA's in case of rekeying" ? Regards, Saravanan N On Fri, Jun 22, 2012 at 10:32 AM, Andreas Steffen < [email protected]> wrote: > With IKEv2, sending a delete notification for the IKE_SA implicitly > means that all dependent CHILD_SAs are automatically deleted, too. > > Regards > > Andreas > > On 06/22/2012 06:47 PM, SaRaVanAn wrote: > > Hi all, > > > > I have a formed a tunnel between Cisco Vpn Client and Strongswan VPN > > server. > > After some time, I stopped IPsec service in strongswan, its sending only > > a delete > > payload of protocol ID 1( IKE_SA),its not sending delete payload for > > CHILD_SA of protocol ID 2, in case of Ikev2, but its working fine in > IKEV1. > > > > Please provide your input on this. > > > > > > Regards, > > Saravanan N > > ====================================================================== > Andreas Steffen [email protected] > strongSwan - the Linux VPN Solution! www.strongswan.org > Institute for Internet Technologies and Applications > Und >
_______________________________________________ Users mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/users
