<br>Hi list,<br><br>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.9 on kernel 2.6.18 still using klips.<br><br>However, when we start ipsec on the upgraded server, we got this error message :
<br>ROOT@NEW-2.4.9:/home/jean-michel# /etc/init.d/ipsec start<br>ipsec_setup: Starting Openswan IPsec 2.4.9...<br>ipsec_setup: /usr/local/libexec/ipsec/tncfg: Socket ioctl failed on attach -- No such device. Is the physical device valid?
<br>ipsec_setup: SIOCSIFFLAGS: No such device<br><br><br>Comparing to another server with old versions : <br><br>ROOT@OLD-2.4.7:/home/jean-michel# cat /proc/net/ipsec_tncfg<br>ipsec0 -> NULL mtu=16260(0) -> 0<br>ipsec1 -> NULL mtu=0(0) -> 0
<br>ipsec2 -> NULL mtu=0(0) -> 0<br>ipsec3 -> NULL mtu=0(0) -> 0<br>ROOT@OLD-2.4.7:/home/jean-michel# ipsec tncfg --attach --virtual ipsec0 --physical eth0<br>ROOT@OLD-2.4.7:/home/jean-michel#<br>ROOT@OLD-2.4.7
:/home/jean-michel# cat /proc/net/ipsec_tncfg<br>ipsec0 -> eth0 mtu=16260(1500) -> 1500<br>ipsec1 -> NULL mtu=0(0) -> 0<br>ipsec2 -> NULL mtu=0(0) -> 0<br>ipsec3 -> NULL mtu=0(0) -> 0<br><br><br>Strangely, on the upgraded server, the proc/net/ipsec_tncfg seems not populated :
<br>ROOT@NEW-2.4.9:/home/jean-michel# cat /proc/net/ipsec_tncfg<br>ipsec0 -> NULL mtu=0(0) -> 0<br>ipsec1 -> NULL mtu=0(0) -> 0<br>ipsec2 -> NULL mtu=0(0) -> 0<br>ipsec3 -> NULL mtu=0(0) -> 0<br>ROOT@NEW-2.4.9
:/home/jean-michel# ipsec tncfg --attach --virtual ipsec0 --physical eth0<br>/usr/local/libexec/ipsec/tncfg: Socket ioctl failed on attach -- No such device. Is the physical device valid?<br><br>Any idea?