ipsec__plutorun: 104 "z2" #1: STATE_MAIN_I1: initiate ... could not start conn "z2

Thread: ipsec__plutorun: 104 "z2" #1: STATE_MAIN_I1: initiate ... could not start conn "z2

Search this list only Search all lists
ipsec__plutorun: 104 "z2" #1: STATE_MAIN_I1: initiate ... could not start conn "z2
	2007-06-14 03:17:35
Hello swan experts, I've setup openswan to tunel between 2 networks. My config comes below. The problem is that tunel is working (i have connectivity between networks) but, when i start ipsec, a strange message appear in my syslog (on booths sides): Jun 13 17:52:59 nx ipsec__plutorun: 104 "z2" #1: STATE_MAIN_I1: initiate Jun 13 17:52:59 nx ipsec__plutorun: ...could not start conn "z2" And tunel comes up!!!! And yes, on the oposite side, ipsec is already running!!!! Is a bug or a feature? If not a bug, how can be convinced openswan to display more info and/or turn off this stupid message? Trying to add plutodebug=all in ipsec.conf doesn't add more verbosity to openswan! [rootnx ~]# cat /etc/issue CentOS release 4.5 (Final) Kernel r on an m [rootnx ~]# [rootnx ~]# uname -r 2.6.9-55.EL [rootnx ~]# [rootnx ~]# rpm -q openswan openswan-2.4.8-1 [rootnx ~]# Openswan has been compiled by me using rpmbuild -ta openswan-2.4.8.tar.gz from openswan website! [rootnx ~]# service ipsec start [rootnx ~]# tail -f /var/log/messages Jun 13 17:52:59 nx ipsec_setup: ...Openswan IPsec started Jun 13 17:52:59 nx ipsec_setup: Starting Openswan IPsec U2.4.8 /K2.6.9-55.EL... Jun 13 17:52:59 nx ipsec__plutorun: 104 "z2" #1: STATE_MAIN_I1: initiate Jun 13 17:52:59 nx ipsec__plutorun: ...could not start conn "z2" [rootnx ~]# cat /etc/ipsec.conf version 2.0 conn z2     authby=secret     left=1.2.3.4     leftsubnet= 192.168.13.0/24     leftnexthop=1.2.3.111     right=5.6.7.8     rightsubnet= 10.0.0.0/24    ; rightnexthop=5.6.7.222     keyexchange=ike  ;   auth=esp     esp=3des-md5-96     keylife=8h     pfs=no     auto=start include /etc/ipsec.d/examples/no_oe.conf [rootnx ~]# Any hints, Alx