[Openswan Users] Which Free or OpenSWAN on Debian testing (2.6.3 kernel)?

[Joost Kraaijeveld]

Hi Ken,

Ken Bantoft schreef:
> Um... which README is this?  Openswan 2.x supports Kernels
> 2.4 *and* 2.6.
The README from OpenSWAN 2.1.2 rc3, line 94.

> Our README explicitly states so, and gives installation
> instructions for both kernels.
Following the instructions, I did not get a working tunnel (which, thanks to Paul Wouters, worked with the same configuration files on a modified RedHat 8.0).

I get the follwing errors:

Directly after installation (with an empty configuration file):

May  2 15:25:33 linuxbuiten ipsec_setup: Starting Openswan IPsec 2.1.2rc3...
May  2 15:25:33 linuxbuiten ipsec_setup: insmod: can't read 'ipsec': No such file or directory
May  2 15:25:34 linuxbuiten ipsec_setup: insmod /lib/modules/2.6.3-1-686/kernel/net/key/af_key.ko
May  2 15:25:34 linuxbuiten ipsec_setup: insmod /lib/modules/2.6.3-1-686/kernel/net/ipv4/ah4.ko
May  2 15:25:34 linuxbuiten ipsec_setup: insmod /lib/modules/2.6.3-1-686/kernel/net/ipv4/esp4.ko
May  2 15:25:34 linuxbuiten ipsec_setup: insmod /lib/modules/2.6.3-1-686/kernel/net/ipv4/ipcomp.ko
May  2 15:25:34 linuxbuiten ipsec_setup: insmod /lib/modules/2.6.3-1-686/kernel/net/xfrm/xfrm_user.ko
May  2 15:25:34 linuxbuiten ipsec_setup: KLIPS ipsec0 on eth0 213.46.144.131/255.255.255.0 broadcast 213.46.144.255

And with an operational configuration file:

May  2 18:26:02 linuxbuiten ipsec_setup: Starting Openswan IPsec U2.1.2rc3/K2.6.3-1-686...
May  2 18:26:02 linuxbuiten ipsec_setup: KLIPS ipsec0 on eth0 213.46.144.131/255.255.255.0 broadcast 213.46.144.255
May  2 18:26:04 linuxbuiten ipsec_setup: ...Openswan IPsec started
May  2 18:26:07 linuxbuiten ipsec__plutorun: 003 "askesis-xtdnet": prepare-client command exited with status 127
May  2 18:26:07 linuxbuiten ipsec__plutorun: 003 "askesis-xtdnet": route-client command exited with status 127
May  2 18:26:07 linuxbuiten ipsec__plutorun: 025 "askesis-xtdnet": could not route
May  2 18:26:07 linuxbuiten ipsec__plutorun: ...could not route conn "askesis-xtdnet"
May  2 18:26:07 linuxbuiten ipsec__plutorun: 003 "askesis-solve-i-t": prepare-client command exited with status 127
May  2 18:26:07 linuxbuiten ipsec__plutorun: 003 "askesis-solve-i-t": route-client command exited with status 127
May  2 18:26:07 linuxbuiten ipsec__plutorun: 003 "askesis-solve-i-t": down-client command exited with status 127
May  2 18:26:07 linuxbuiten ipsec__plutorun: 025 "askesis-solve-i-t": could not route
May  2 18:26:07 linuxbuiten ipsec__plutorun: ...could not route conn "askesis-solve-i-t"
May  2 18:26:07 linuxbuiten ipsec__plutorun: 104 "askesis-xtdnet" #1: STATE_MAIN_I1: initiate
May  2 18:26:07 linuxbuiten ipsec__plutorun: ...could not start conn "askesis-xtdnet"
May  2 18:26:07 linuxbuiten ipsec__plutorun: 104 "askesis-solve-i-t" #2: STATE_MAIN_I1: initiate
May  2 18:26:07 linuxbuiten ipsec__plutorun: ...could not start conn "askesis-solve-i-t"

Any ideas????

Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: J.Kraaijeveld at Askesis.nl
web: www.askesis.nl