| | 5 | <pre>>>What was happening<br />>>earlier was that I built openvpn first, then realized I needed to build<br />>>the tun/tap kernel module, so built that and then rebuilt openvpn - but<br />>>configure (god bless it) used the cached result of NOT finding if_tun.h.<br /> >> I cleared configure's cache and rebuilt it again - this time it found<br />>>"tun/tap v1.4". Now I'm onto a new set of problems though. Now I get:<br />>><br />>>34: Cannot ioctl TUNSETIFF tun: File descriptor in bad state (errno=77)<br />><br />> Though I've never seen this error personally, it has been talked about<br />> extensively on the vtun list (another tunneling daemon that uses the TUN/TAP<br />> driver).<br />><br />> Go to <a href="http://sourceforge.net/mailarchive/forum.php?forum_id=1826"> http://sourceforge.net/mailarchive/forum.php?forum_id=1826</a><br />><br />> and search for "bad state".<br />><br />> It appears to be caused by a mismatch between the tun/tap kernel module and<br />> the kernel itself.<br />><br />> What kernel version are you using?<br />><br />> Because in versions 2.4.6 and higher, the TUN/TAP module is integral to the<br />> kernel -- if you try to build an external version of the module, rather than<br />> using the one already bundled, it will likely fail.<br /><br />Also I've read a few posts that suggest that /usr/src/linux needs to point<br />to headers that match the running kernel. Depending on what Sean has, it<br />may be worthwhile to ensure all the various versions<br />(kernel/headers/tunTap) all match.</pre> |
