[Vtun-Users] TUN/TAP problems in 2.4.6-2.4.14
Status: Inactive
Brought to you by:
mtbishop
|
From: Maksim K. <ma...@qu...> - 2001-11-17 07:45:46
|
Folks, Summary on TUN/TAP problems with recent kernels. Problem #1: Can't allocate tunX or tapX. File descriptor in bad stage (EBADFD). Reason: TUN/TAP API change in kernel 2.4.6. Solution: Copy /usr/src/linux/include/linux/if_tun.h to /usr/include/linux/if_tun.h. Upgrade VTun to version 2.5.b1 and recompile. Code in CVS has support for both old (pre 2.4.6) and new APIs. 2.5b2 final will be released soon. Problem #2: Can't allocate tunX or tapX. Invalid argument (EINVAL). Reason: Bug in kernel networking code (linux/net/code/dev.c) introduced somewhere in 2.4.10 - 2.4.14. Solution: This bug has been fixed in 2.4.5-pre2. Upgrade kernel to at least 2.4.15-pre5. Or do not use static device names in vtund.conf. ie comment out "device" options. Dynamic device allocation works just fine. Regards Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated ma...@qu... http://bluez.sf.net http://vtun.sf.net |