[Openswan Users] Problem : unregister_netdevice: waiting for ipsec0 to become free

[Jean-Michel Bonnefond]

Thanks Paul,

First sorry for the delay to answer.

You're right it come from the 2.4.13 klips stack. I've compiled 2 versions,
using the same server, same kernel, same openswan version and here is the
result :

localhost:~# ipsec --version
Linux Openswan U2.4.13/K2.4.12 (klips)
See `ipsec --copyright' for copyright information.
localhost:~# /etc/init.d/ipsec stop
ipsec_setup: Stopping Openswan IPsec...
localhost:~# ipsec --version
Linux Openswan U2.4.13/K(no kernel code presently loaded)
See `ipsec --copyright' for copyright information.


localhost:~# ipsec --version
Linux Openswan 2.4.13 (klips)
See `ipsec --copyright' for copyright information.
localhost:~# /etc/init.d/ipsec stop
Message from syslogd at localhost at Wed Sep 17 15:35:02 2008 ...
localhost kernel: unregister_netdevice: waiting for ipsec0 to become free.
Usage count = -2

However there is not a lot of differencies between the two versions, appart
some special code for kernel 2.6.24, and the proc_net renamed LINUX_PROCNET,
so I'm a bit confusing.

I'll try to make some test modifiyng the code tommorrow.

Jean-Michel.


2008/9/16 Paul Wouters <paul at xelerance.com>

> On Tue, 16 Sep 2008, Jean-Michel Bonnefond wrote:
>
>  I'm currently using openswan 2.4.9 over a self compiled linux kernel
>> 2.6.18 with the Klips stack instead of netkey.
>>
>> I'm trying to upgrade my kernel to the debian patched kernel 2.6.18 (wich
>> include security patches that I need) and I
>> would like to upgrade openswan in the same time.
>>
>> I'm not sure of which new version to choose.
>>
>
> Pick 2.4.13. It should work fine on 2.6.18 kernels. Unless you need IKEv2
> functionality (not likely) or hardware
> crypto offload.
>
>  What is the major differences between openswan 2.4.13 and 2.6.16?
>>
>
> 2.4.13 is the last of the 2.4 series. 2.6.x still has a few small bugs. It
> might not hit you, but you
> can avoid them for now by using 2.4.13.
>
>  Are the 2.6.x development versions leadind to v3 ?
>>
>
> 3.x is currently a side branch. Ideally it will merged into the 2.6 tree.
> But it all depends a bit on where
> crypto hardware acceleration in the Linux kernel is going to. (OCF vs
> acrypto)
>
>  localhost:~# /etc/init.d/ipsec stop
>> Message from syslogd at localhost at Tue Sep 16 08:01:43 2008 ...
>> localhost kernel: unregister_netdevice: waiting for ipsec0 to become free.
>> Usage count = -6
>>
>
> That looks like a KLIPS bug.... You could try comparing some code, but it's
> probably not an easy
> bug to find and fix.
>
> Paul
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openswan.org/pipermail/users/attachments/20080918/3c31ff7a/attachment.html