Tunnelblick在Mac OS上重复断开连接的解决办法

最近系统升级到Mountain lion以后，Tunnelblick就出现反复连接断开的状况，开始还以为是Tunnelblick的版本问题，后来Google了下，找到解决方法：

1.打开Tunnelblick的设置窗口，点击[设置]栏下方的[高级]按钮

2.在[高级]设置内的[链接中]栏内，把[搜索域]的[当改变其它时]选项设置为[忽略]。这样设置完毕，Tunnelblick的反复连接断开问题就解决了。

附上原英文的解决方法，我的烂英文水平居然看懂了。

Reported by project member jkbull…@gmail.com, Mar 26, 2012

On OS X 10.8.1 or 10.8.2 (“Mountain Lion”) some configurations that use “Set nameserver” causes Tunnelblick to continuously disconnect and reconnect the configuration.

The disconnect/reconnect will appear in the log as something similar to:

2012-03-26 22:17:33 *Tunnelblick process-network-changes: SearchDomains changed from

*

*                     to

*                    <array> {

*                    0 : openvpn

*                    }

*                    pre-VPN was

*

To work around this problem while still using “Set nameserver”, you can do the following:

Click the “Advanced” button on the “Settings” tab for the configuration, then select the “While Connected” tab. Change the setting for “Search domain” in the right-hand column (the “When changes to anything else” column) from “Restart connection” to “Ignore”. That will ignore the changes to “Search domain”.

Anyone with a similar problem on Mountain Lion but not involving “SearchDomains”, please post the extract from the log that is similar to the above extract, including the name of the item that changed.

A connection is established, but drops out or is restarted after a few minutes, or DNS stops working after a few minutes

This can have several causes:

• Another computer on your network is attempting to connect to the VPN using the same credentials.
• You have a version of Tunnelblick earlier than 3.1beta04 and have both "Set nameserver" and "Monitor connection" checked. When DHCP is renewed, the changes can cause earlier versions of Tunnelblick to restart the connection. Update to the latest version of Tunnelblick.
• You have "Monitor connection" UNchecked. When DHCP is renewed, the change is ignored (because "Monitor connection" isn't checked) and the VPN-supplied DNS server is replaced with the DHCP-supplied server. Often a DHCP-supplied server will only respond to queries which originate within that network. Since the DNS queries originate from the VPN, which is outside of that network, the queries will not be answered. Update to the latest version of Tunnelblick and put a check next to "Monitor network".