On Thu, Nov 24, 2016 at 7:30 PM, Jason Haar <jason_h...@trimble.com> wrote: > > On Fri, Nov 25, 2016 at 11:48 AM, Mathias Jeschke <openvpn-us...@0xaffe.de> > wrote: >> >> Why not run the openvpn binary that comes with Tunnelblick? > > > Wow - I have no idea how I missed that! Thanks for spelling out the bleeding > obvious to me - I must be getting old! :-)
FYI: Current releases of Tunnelblick are for OS X 10.7.5 and up (64-bit Intel) only. Version 3.5.11 works on OS X 10.4 and up, and on Intel or PPC and is available on Tunnelblick's Deprecated Downloads page, https://tunnelblick.net/downloadsDeprecated.html. OS X 10.6.8 and higher include "utun" drivers, making loading of the tun kext unnecessary. As long as there is not a --dev-type option specifying a "tun" device, OpenVPN will use the built-in "utun" driver. Tunnelblick loads the "tun" driver automatically if it is needed, but if you are using "raw" OpenVPN and have a mix of pre-10.6.8 and 10.6.8+ systems, you'll have to do it yourself. It's a bit complicated because some "tun" drivers work only on some versions of OS X. Another complication is that Tunnelblick usually includes two or more versions of OpenVPN binaries, each in a separate subfolder of /Applications/Tunnelblick.app/Contents/Resources/openvpn. There is also a symlink in that folder that links directly to the "default" OpenVPN binary, usually the lowest version using OpenSSL. That's useful for scripts because Tunnelblick can be updated (with new versions of OpenVPN) without breaking a "static" link to a "stable" OpenVPN. (The last couple of Tunnelblick releases have included binaries built with OpenSSL and with LibreSSL, which complicates the choices even more!) ------------------------------------------------------------------------------ _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
