Well, since macOS 10.13 (or was it 12?) the use of kernel extensions (.kext) is discouraged, and in 10.15, due to all the warnings, nearly unusable.

See Creating and Installing a Tunnelblick VPN Configuration for details. (Note that it must be a shared configuration, and that shared configurations must be “Tunnelblick VPN Configurations”, which package together the configuration file and key and certificate files. Instead of steps 15-17, just set up Tunnelblick to start the configuration “When computer starts”. They can (even when using the “openvpn-down-root” plugin) cause problems if transmission errors make it necessary for OpenVPN to restart a connection to the server and routing is done by OpenVPN (which is often the case). In step 14, I recommend leaving “ user nobody” and “ group nobody” lines intact. (easy-rsa is accessed via the “Utilities” tab in Tunnelblick’s “VPN Details…” window.) Steps 1-5 can be skipped, because Tunnelblick includes tun/tap drivers and easy-rsa. However, recent beta versions of Tunnelblick make much of this unnecessary. Thanks for this article - it is an easy step-by-step guide. This will allow your system to create virtual network devices. Please read his comment on the bottom of the article before doing all this :)ĭownload and install the package.

IMPORTANT NOTE: Jon Bullard (developer of TunnelBlick) has commented that with recent (beta) versions, much of this article is no longer needed. But to connect to your own Mac or maybe a server you own or are the maintainer for at work, you will need an OpenVPN Server set-up. I sincerely hope the TunnelBlick development team will take the time and effort to rebuild the client to use the new KPIs in macOS Big Sur, but latest response suggest they have no interest to do so :(Īn OpenVPN Client is easy, just download Tunnelblick. Due to deprecation of kernel extensions in MacOS (10.12 and newer) OpenVPN seems to be defunct on macOS (at least for private servers), please see my comment.

Tunnelblick yosemite