Feature #1668
closed
OpenVPN Client Export support Tunnelblick
0%
Description
TunnelBrick is an opensource MacOSX OpenVPN client that seems to be pretty active. https://code.google.com/p/tunnelblick/
It would be nice if the OpenVPN Client export could generate a preconfigured package for OSX using this project similar to how the export for the Windows OpenVPN Gui works now. They do have some information in the project wiki here about creating deployable versions. https://code.google.com/p/tunnelblick/wiki/zCusDeployed
They also do have a configuration format that if it's not possible to create a package it would be nice to have the option to export it's configuration similar to how Viscosity is currently supported. https://code.google.com/p/tunnelblick/wiki/zConfigT#Creating_a_Tunnelblick_VPN_Configuration
Updated by David Miller over 13 years ago
I typo'ed the name of the client in the subject and don't have permissions to correct it. Could someone please correct that if possible so that people searching for tunnelblick can find this bug. Sorry about that.
Updated by Chris Buechler over 13 years ago
- Subject changed from OpenVPN Client Export support TunnelBrick to OpenVPN Client Export support Tunnelblick
The config archive works fine for Tunnelblick.
Updated by David Miller over 13 years ago
Ok good to know. I don't have a Mac to try it out on but I know some of my users have Macs at home so the support questions are bound to happen at some point as I roll this out to them.
Updated by Mathieu Simon over 12 years ago
Creating a Tunnelblick configuration (not a installer bundle) seems pretty straightforward as the uncompressed configuration archive simply had to sufixed by ".tblk" - which makes Tunnelblick recognize this folder as configuration bundle.
I did this manually for us by extracting the config bundle, renaming the folder and creating a tar.gz file.
So far, this seemed to work also for my co-workers.
Updated by Jim Pingle almost 12 years ago
- Status changed from New to Closed
Just tested this and the current beta (didn't test the release) imported an "Other" type Inline config without any fuss. Connected the first time, no adjustments needed. Given that, I don't think we need to modify anything for Tunnelblick, we just need to document that it works with the Inline export.