THE LATEST VERSION OF THIS DOCUMENT is at http://code.google.com/p/tunnelblick/wiki/KnownIssues.

PLEASE DO discuss any problems on the Tunnelblick Discussion List before initiating an Issue. Issues are usually only looked at by the developers; the Discussion List has a broader audience of members who might be able to help!

PLEASE DO NOT post comments at the bottom of this page. Use the Tunnelblick Discussion List instead.

The following are known problems or limitations in Tunnelblick version 3.0b24:

• The standard scripts that "Set nameserver" uses handle DNS for most common setups. You must use custom scripts to do anything else. See the Using Tunnelblick wiki for details.

• When attempting to connect to a VPN, Tunnelblick may fail to load tun.kext and tap.kext. This can happen when another program, or another version of Tunnelblick, has loaded different versions of tun.kext and tap.kext. For example, the Cisco VPN client loads tun.kext and tap.kext at system startup, and they must be unloaded for Tunnelblick to work. Viscosity loads tun.kext and tap.kext when it is running. This problem may be avoided (for Viscosity) by quitting Viscosity, or (for Cisco) by entering the following command:

  sudo /System/Library/StartupItems/CiscoTUN stop 

• If "Set nameserver" is checked, all "up" and "down" options in the OpenVPN configuration file will be ignored. To work around this, include appropriate parts of the standard up/down scripts in your own scripts and do not check "Set nameserver". (The reason for this is that OpenVPN's "down-pre" option cannot be used with the standard "Set nameserver" down script, but may be used by custom scripts, so the two scripts cannot be used together.)

• Localization is not complete. We need additional translations to Catalan, German, Spanish, French, Japanese, Korean, and Norwegian (Norsk Bokmal). If you can help with these or any other languages, please contact project committer Jon.

PLEASE DO NOT post comments here. Use the Tunnelblick Discussion List instead.