[strongSwan] different output of 'ipsec statusall' command in version 4.5.3 and 5.0.2 for tunnels configured with IKEv1

Hi List, I have created a tunnel between two machine M1 and M2. Tunnel seems to be created successfully and I am also able to ping between two endpoints. Configuration at both ends is as follows: M1 (Octean): IKEv1 Ipsec version: Linux strongSwan U4.5.3/K2.6.32.60-1-lfs130202-ci1-fct Output:

Re: [strongSwan] different output of 'ipsec statusall' command in version 4.5.3 and 5.0.2 for tunnels configured with IKEv1

Hi, Linux strongSwan U4.5.3/K2.6.32.60-1-lfs130202-ci1-fct Linux strongSwan U5.0.2/K2.6.18-128.el5 Why is there such a difference between two outputs? strongSwan 5.x introduces a completely new implementation of the IKEv1 protocol in the charon daemon (that previously handled IKEv2 only).

Re: [strongSwan] different output of 'ipsec statusall' command in version 4.5.3 and 5.0.2 for tunnels configured with IKEv1

Hi Martin, Thanks for your quick response. But then why its not showing SA as ESTABLISHED while its indeed ESTABLISHED and working fine for IKEv1: M1 (Octean): IKEv1 Ipsec version: Linux strongSwan U4.5.3/K2.6.32.60-1-lfs130202- ci1-fct Output: root@172:~ ipsec status 000 conn1: