<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>Re: [Openswan Users] KLIPS crashes on kernel 2.6.25></TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<BR>
<P><FONT SIZE=2>> Try the attached patch,<BR>
<BR>
As usual, it works. I was able to compile klips with cryptoapi on Centos 5.3. Sadly, even with cryptoapi, the problem while loading ipsec0 and the crash while unloading ipsec.ko persists:<BR>
<BR>
Nov 3 20:12:44 localhost ipsec_setup: Starting Openswan IPsec 2.6.24rc1...<BR>
Nov 3 20:12:44 localhost ipsec_setup: Using KLIPS/legacy stack<BR>
Nov 3 20:12:44 localhost kernel: padlock: VIA PadLock not detected.<BR>
Nov 3 20:12:44 localhost kernel: padlock: VIA PadLock not detected.<BR>
Nov 3 20:12:45 localhost kernel: klips_info:ipsec_init: KLIPS startup, Openswan KLIPS IPsec stack version: 2.6.24rc1<BR>
Nov 3 20:12:45 localhost kernel: NET: Registered protocol family 15<BR>
Nov 3 20:12:45 localhost kernel: klips_info:ipsec_alg_init: KLIPS alg v=0.8.1-0 (EALG_MAX=255, AALG_MAX=251)<BR>
Nov 3 20:12:45 localhost kernel: klips_info:ipsec_alg_init: calling ipsec_alg_static_init()<BR>
Nov 3 20:12:45 localhost kernel: KLIPS cryptoapi interface: alg_type=15 alg_id=12 name=aes keyminbits=128 keymaxbits=256, found(0)<BR>
Nov 3 20:12:45 localhost kernel: KLIPS cryptoapi interface: alg_type=15 alg_id=253 name=twofish keyminbits=128 keymaxbits=256, found(0)<BR>
Nov 3 20:12:45 localhost kernel: KLIPS cryptoapi interface: alg_type=15 alg_id=252 name=serpent keyminbits=128 keymaxbits=256, found(0)<BR>
Nov 3 20:12:45 localhost kernel: KLIPS cryptoapi interface: alg_type=15 alg_id=6 name=cast5 keyminbits=128 keymaxbits=128, found(0)<BR>
Nov 3 20:12:45 localhost kernel: KLIPS cryptoapi interface: alg_type=15 alg_id=7 name=blowfish keyminbits=96 keymaxbits=448, found(0)<BR>
Nov 3 20:12:45 localhost kernel: KLIPS cryptoapi interface: alg_type=15 alg_id=3 name=des3_ede keyminbits=192 keymaxbits=192, found(0)<BR>
Nov 3 20:12:45 localhost ipsec_setup: KLIPS debug `none'<BR>
Nov 3 20:12:45 localhost kernel:<BR>
Nov 3 20:12:45 localhost ipsec_setup: KLIPS ipsec0 on eth0 10.1.1.7/255.0.0.0 broadcast 10.255.255.255<BR>
Nov 3 20:12:45 localhost ipsec_setup: /usr/local/libexec/ipsec/tncfg: Socket ioctl failed on attach -- No such device. Is the virtual device valid? Is the ipsec module linked into the kernel or loaded as a module?<BR>
Nov 3 20:12:45 localhost ipsec_setup: SIOCSIFADDR: No such device<BR>
Nov 3 20:12:45 localhost ipsec_setup: ipsec0: unknown interface: No such device<BR>
Nov 3 20:12:45 localhost ipsec_setup: SIOCSIFBRDADDR: No such device<BR>
Nov 3 20:12:45 localhost ipsec_setup: ipsec0: unknown interface: No such device<BR>
Nov 3 20:12:45 localhost ipsec_setup: SIOCSIFNETMASK: No such device<BR>
Nov 3 20:12:46 localhost ipsec_setup: ...Openswan IPsec started<BR>
<BR>
<BR>
No pressure, just thought I would let you know. Any idea what this is?<BR>
<BR>
I spent the whole afternoon testing a fedora 7 install, kernel 2.6.23, openswan-2.6.24rc1 klips whith Vista and XP clients and was not able to reproduce the tunnel instability I reported before. I'll keep testing on fedora and will also test on Ubuntu 8.03 tomorrow and let you know.<BR>
<BR>
Thanks again David,<BR>
<BR>
Giovani<BR>
</FONT>
</P>
</BODY>
</HTML>