tun device: File descriptor in bad state(77)
Hi there!
I graded up from kernel 2.4.5 to 2.4.8 and now have trouble with vtund 2.5b1 and tun 1.1.
vtund[532]: Session st_sm[217.230.44.100:1577] opened vtund[532]: Can't allocate tun device. File descriptor in bad state(77) vtund[532]: Session st_sm closed
Also
root:~# cat /dev/net/tun cat: /dev/net/tun: File descriptor in bad state
Tried to recompile both packages and created a new device but without effect.
Best regards,
Max
Quoted 8 lines
Hi there!
I graded up from kernel 2.4.5 to 2.4.8 and now have trouble with vtund 2.5b1 and tun 1.1.
vtund[532]: Session st_sm[217.230.44.100:1577] opened vtund[532]: Can't allocate tun device. File descriptor in bad state(77) vtund[532]: Session
st_smclosed
Try using the included tun 1.4 thats in the kernel source. Vtund might need a small patch to work, I'm not sure about your version. Look at this patch:
http://www.sannes.org/secnet/secnet-1.0d-linux-2.4.diff
It should apply on vtund 2.4 at least (secnetd is just a different "version" of vtund with stronger encryption and some bugfixes). If it does not apply, try readning it and see what it does (it's nothing big, two additions of #includes.)
--
Regards,
André Tomt
[email protected]
Some bits changed under vtun at 2.4.6 IIRC.
I patched vtun for my own use with patches from Kevin Fleming, made rpms, and called it 2.4a. It's been working fine here -
Perhaps someone else on the vtun team can offer more recent information.
cu
jjs
Quoted 25 lines · Max Schattauer
Hi there!
I graded up from kernel 2.4.5 to 2.4.8 and now have trouble with vtund 2.5b1 and tun 1.1.
vtund[532]: Session st_sm[217.230.44.100:1577] opened vtund[532]: Can't allocate tun device. File descriptor in bad state(77) vtund[532]: Session
st_smclosedAlso
root:~# cat /dev/net/tun cat: /dev/net/tun: File descriptor in bad stateTried to recompile both packages and created a new device but without effect.
Best regards,
Max
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 3 lines
I graded up from kernel 2.4.5 to 2.4.8 and now have trouble with vtund 2.5b1 and tun 1.1.
Please read VTun mailing list archives.
Max
Maksim Krasnyanskiy
Senior Kernel Engineer
Qualcomm Incorporated