[Openswan dev] ipsec__plutorun: 104 "z2" #1: STATE_MAIN_I1: initiate ...could not start conn "z2"

Paul Wouters paul at xelerance.com
Thu Jun 14 10:23:44 EDT 2007

On Thu, 14 Jun 2007, Linux User wrote:

> 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!

In fact, we would prefer a full log from start to tunnel is up, WITHOUT
using plutodebug= or klipsdebug.

Note that most of the logs end up in /var/log/secure, not /var/log/messages.


More information about the Dev mailing list