[strongSwan] Some weird thing

Ali Masoudi masoudi1983 at gmail.com
Tue Sep 25 15:25:38 CEST 2012


Hello


There is an issue when I'm working with strongswan. Sometimes when I
put some tunnels "up" or "down" with command "ipsec down tunnel_name",
the whole SAs (IKE and CHILD) are erased. I also tried to delete
CHILD_SAs first, and then IKE_SAs. but in this method too, same thing
happened.

For example, here is some lines from the log, I don't know why charon
receives critical signal after successfully destroying IKE_SA for
mytun1:

Sep 25 06:37:23 14[IKE] <214-1|1> IKE_SA mytun1[1] state change:
DELETING => DESTROYING
Sep 25 06:37:23 14[MGR] check-in and destroy of IKE_SA successful
Sep 25 06:37:23 14[DMN] thread 14 received 11
Sep 25 06:37:23 14[DMN] killing ourself, received critical signal
Sep 25 06:37:28 00[DMN] Starting IKE charon daemon (strongSwan 5.0.0,
Linux 2.6.34.1, i686)
Sep 25 06:37:28 00[LIB] plugin 'aes': loaded successfully
Sep 25 06:37:28 00[LIB] plugin 'des': loaded successfully
Sep 25 06:37:28 00[LIB] plugin 'sha1': loaded successfully
Sep 25 06:37:28 00[LIB] plugin 'sha2': loaded successfully

Is there anybody else who has this problem? What is the best way to
bring down a tunnel? I'm using kernel 2.6.34.1 and strongswan 5.0.0.

Thanks in advance
Ali




More information about the Users mailing list