[Openswan Users] ipsec tncfg doesn't attach device

[Jean-Michel Bonnefond]

Hi list,

We are migrating our debian sarge server to etch. We currently use openswan
2.4.7 on kernel 2.6.8 with Klips stack. Our new OS is using openswan
2.4.9on kernel
2.6.18 still using klips.

However, when we start ipsec on the upgraded server, we got this error
message :
ROOT at NEW-2.4.9:/home/jean-michel# /etc/init.d/ipsec start
ipsec_setup: Starting Openswan IPsec 2.4.9...
ipsec_setup: /usr/local/libexec/ipsec/tncfg: Socket ioctl failed on attach
-- No such device.  Is the physical device valid?
ipsec_setup: SIOCSIFFLAGS: No such device


Comparing to another server with old versions :

ROOT at OLD-2.4.7:/home/jean-michel# cat /proc/net/ipsec_tncfg
ipsec0 -> NULL mtu=16260(0) -> 0
ipsec1 -> NULL mtu=0(0) -> 0
ipsec2 -> NULL mtu=0(0) -> 0
ipsec3 -> NULL mtu=0(0) -> 0
ROOT at OLD-2.4.7:/home/jean-michel# ipsec tncfg --attach --virtual ipsec0
--physical eth0
ROOT at OLD-2.4.7:/home/jean-michel#
ROOT at OLD-2.4.7:/home/jean-michel# cat /proc/net/ipsec_tncfg
ipsec0 -> eth0 mtu=16260(1500) -> 1500
ipsec1 -> NULL mtu=0(0) -> 0
ipsec2 -> NULL mtu=0(0) -> 0
ipsec3 -> NULL mtu=0(0) -> 0


Strangely, on the upgraded server, the proc/net/ipsec_tncfg seems not
populated :
ROOT at NEW-2.4.9:/home/jean-michel# cat /proc/net/ipsec_tncfg
ipsec0 -> NULL mtu=0(0) -> 0
ipsec1 -> NULL mtu=0(0) -> 0
ipsec2 -> NULL mtu=0(0) -> 0
ipsec3 -> NULL mtu=0(0) -> 0
ROOT at NEW-2.4.9:/home/jean-michel# ipsec tncfg --attach --virtual ipsec0
--physical eth0
/usr/local/libexec/ipsec/tncfg: Socket ioctl failed on attach -- No such
device.  Is the physical device valid?

Any idea?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openswan.org/pipermail/users/attachments/20071009/34327ce0/attachment.html