[Openswan Users] 2.4.0 trouble

[Ethy H. Brito]

On Tue, 04 Oct 2005 14:24:38 -0700
Christopher Malott <chris at travelconnection.com> wrote:

> If you want the ipsecX interface on 2.6 you will need utilize KLIPS 
> instead of NETKEY. You can either choose to build KLIPS as a module, or 
> patch your kernel and compile it in statically. You can find the KLIPS 
> patch on the openswan.org website.

How will I know if its working if there are no interfaces criated?

I got this
Oct  4 21:07:49 cressem ipsec_setup: KLIPS ipsec0 on eth0 200.231.48.37/255.255.255.224 broadcast 200.231.48.63 
Oct  4 21:07:49 cressem ipsec_setup: ...Openswan IPsec started
Oct  4 21:07:49 cressem ipsec_setup: Starting Openswan IPsec U2.4.0/K2.6.13.2...
Oct  4 21:07:50 cressem ipsec__plutorun: 104 "cressem" #1: STATE_MAIN_I1: initiate
Oct  4 21:07:50 cressem ipsec__plutorun: ...could not start conn "cressem"

and no clues what is wrong. The error messages could be more clear.

I am about to give up kernel 2.6, downgrade to 2.4.31 and OpenSwan 2.2.0.

OpenSwan 2.4.0 is too complicated to put it to work!

Ethy