tun/tap Driver for Mac OS X Intel

I’ve built the tun/tap driver for Mac OS X for Tiger on Intel processors. You can download tuntap_tiger-intel-20060604.tar.gz
and the diffs I used to get it to compile and build the packages…

Simply untar the package and double click the tuntap_install.mpkg file to install.

I’ve not actually tested this yet beyond performing an install and ensuring that the kexts loaded – I will be doing so as soon as I get an OpenVPN server going and use Tunnelblick for the client-side.

Please let me know if you run into issues with this.

34 Responses to “tun/tap Driver for Mac OS X Intel”

  1. tim.vanreenen@gmail.com Says:

    There is an issue with your tuntap_tiger-intel-20060604.tar.gz. I untar-ed the package and went to install it however the installer consistently tells me that there is nothing to intall. I tried the startup, tun, and tap, packages seperately and they all said the same thing. The package in 212KB download. I’m wondering if something went wrong when the packages were built. Sorry about that. I’d still like to get a hold of an intel build for the driver if you get it figured out. Thanks

  2. jp Says:

    I had the same problem with it. I had to build my own last time, it wasn’t pretty but it worked until apple released the May “Security” updates.

  3. Matt Says:

    I’ll look into this at my first opportunity. I’m surprised this happened, since I used this to install on my Intel Mac mini.

  4. B Says:

    Same problem, empty installers

  5. jkv@unixcluster.dk Says:

    Yeah, same problem here.

    When installing on my G5 it pops out and asks for password. On my macbook it dont ask for password, just says nothing to install…

  6. Rich Says:

    Same Problem of “Nothing to Load” on this end. Definitely does not like the Intel Core Duo hardware.

  7. jkv@unixcluster.dk Says:

    I made som progress…

    It seems it is the installer which are broken on intel(on my G5 it works flawless), if i unpack and kextload the tap and tun extensions by hand it works…

    /jkv

  8. Dave Says:

    I’m not seeing these problems everyone else is having. It works perfectly here on my new MacBook Pro; just connected to my office via OpenVPN.

  9. jkv@unixcluster.dk Says:

    Anyone got bonjour working with openvpn?

  10. Topper Says:

    I also have the same problem with the installer on my Macbook.

    install.log logs this:

    Package Authoring Error: Infinite loop between <choice> attributes and mixed state aborted.

    which might shed some light on the problem.

  11. brian Says:

    It’s looking like the actual kexts within the .pkgs are still built for PPC, and the installers are broken.

  12. Matt Says:

    The kexts were built on an i386 Mac. I’m pretty certain they are i386 code:

    file Library/Extensions/tun.kext/Contents/MacOS/tun
    Library/Extensions/tun.kext/Contents/MacOS/tun: Mach-O object i386

    The installers are definitely broken somehow – I’m trying to determine how to fix them and correct the issues.

  13. Nick Says:

    Hi Matt,

    Any thoughts on when you may have this issue solved? Thanks for all your work!

    Nick

  14. maik Says:

    Same problem, empty installers.
    But i installed it manually and it’s workin perfect!

    Thanx Matt!

  15. maik Says:

    Same problem, empty installers.
    But i installed it manually and it’s workin perfect!

    Thanx Matt!

  16. JP Says:

    When you say ‘manually installed’ what do you mean? I’ve found the ‘Archive.pax.gz’s in each package, extracted them and moved them to the correct directories, but when I try to kextload the kernel extensions it tells me:
    kextload: extension /Library/Extensions/tap.kext is not authentic (check ownership and permissions)

    I’ve attempted to get the ownerships and auths to be the same as other kexts I have, but with no luck. Any ideas?

  17. JP Says:

    Scrap that! All sorted, you need to:

    cd /Library/Extensions
    sudo chown -R root:wheel tun.kext
    sudo chmod -R go-w tun.kext
    sudo chown -R root:wheel tap.kext
    sudo chmod -R go-w tap.kext

    cheers!

  18. spork Says:

    so, um, what’s the fix for the problem where the installer refuses to install? I gots me no OpenVPN lovin on my Intel MacBook, and I’m not sure how to pull the Archive.pax.gz’s out of the includeded .pkg files.

  19. Matt Says:

    From what I understand, Tunnelblick 3.0 will properly install a tun/tap universal binary. That’s a good way to go until I get the time to solve this problem and update things here.

  20. Nick Says:

    Could someone explain the process of a manual install? In which folders do the files need to be placed?

    Thanks for all the help!

    Nick

  21. Matt Says:

    You have to pull apart the Archive.pax.gz and put the tap.ext and tun.ext folders into /Library/Extensions

    If you want the extensions to load on boot, you’ll need to place the tap and tun folders into /System/Library/StartupItems

  22. Svein Are Says:

    Have the same problem on my MacBook.

    The intel-installer says there is nothing to install.

    The tiger-version (from May 17th) fails during the install, but it creates the files under /Library/Extensions/

    1) Do I have to use the intel one? (will the tiger version NOT work?)

    2) HOW do I extract/install manuall the intel-version (I’m new to OSX)

    3) How do I start the tap-driver once the magic fra post #17 is performed?

  23. Turk Says:

    Ok,I have this installed on my powerbook no problem. The kexts are loaded but the tun and tap devices don’t exist according to ifconfig. Anybody have any suggestions?

  24. Lorenzo Says:

    The problem Turk describe is the same for me!
    The kext are loaded but no network intercaces are present according “ifconfig” command!
    What can I do?

  25. Matt Says:

    You need a program to open the tun/tap device in order for the interface to show up in an ifconfig list. I generally use tun/tap with OpenVPN via Tunnelblick. What are you intending to use tun/tap with?

  26. Lorenzo Says:

    Hi Matt, hhanks for your suggestion.

    I need tun/tap kernel extensions to use it with OpenVPN and Tunnelblick.
    Onestly I didn’t start Openvpn because I didn’t see the interfaces using ifconfig command and I supposed something was wrong with the tun/tap kernel extensions.
    I supposed something was wrong because on a PPC Powerbook where I installed the tun/tap kernel extensions, using ifconfig command I can see the interfaces, and this scenario lead me to this conclusion…
    But now I got to do the test you suggest, to start OpenVPN.

    Thanks
    Lorenzo

  27. Matt Says:

    Tunnelblick actually ships with the tun/tap extensions, so installing it by itself should probably put the kexts in the proper place.

  28. Lorenzo Says:

    Hi Matt:

    I would like to confirm you: “The scenario is exactly as you describe”.

    After I have installed the tun/tap kext extension I can’t see the interfaces using the “ifconfig” command but if I start OpenVpn using TunnleBlick or OpenVpn standalone, the tun interface goes up and work well.
    So what we can say is that there is a different behaviour between kext PPC version and kext Intel version..

    Thanks again,
    Lorenzo

  29. Matt Says:

    From my read of the code for tun/tap, the interfaces don’t show up until used the first time. What you’re saying about ifconfig showing the interfaces only after first use seems to be consistent with that.

  30. Rutt Says:

    This works for me most of the time, but not as reliably as whatever was in tunnelblick 2.
    0.1 on powermacs. I still have a g5 desktop and I used to have a powerbook. On those machines, my VPN would stay up forever as long as there was any network connection. Now I have a MacBook Pro and it’s connection dies regularly and never survives the case being shut and reopened (the old version would). Seems like this version might have some sort of code to sense some sort of network outage and give up. I found nothing obvious in the logs.

  31. Stephen Cooper Says:

    This guy S.Kapp has written a short Howto on getting these drivers installed on an Intel Mac.

    Similar to JPs comments above, but with detail on exactly how to do it including getting the startup item working.

    I made one small change in that I put the startup item in /Library/Startupitems, not /System/Library.

    The permissions were wrong for me on the first reboot, but Mac OSX fixed them for me.

    I have them installed on an Intel Mac Mini (at last) and they work.

    http://journal.virus.org/2007/01/30/openvpn-on-intel-os-x/

  32. Steven Gerendash Says:

    I think it has something to do with previously installed packages I trashed previous tun tap packages from receipts folder and then installation worked. didn’t get startup package to work however don’t know what I need to delete for that. got openvpn to connect once then starting having connection issues. am new to macs so don’t know if my method is appropriate or not just trying it out.

  33. Andrew Says:

    Update: this works well with leopard (10.5) as of right now. You have to go into the tun and the tap packages and delete the Installation Requirements or whatever so that it wont say “Tiger is not installed…”

    Worked with hamachi install anyway.

  34. Matt Says:

    Thanks for the update.

    I have found the easiest way to get Tun/Tap installed is to install Tunnelblick, a great OpenVPN frontend. It includes Universal Binary Tun/Tap kexts.

Leave a Reply