Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frequently leaves behind bad routes causing unreachable host #421

Closed
khazhyk opened this issue Dec 20, 2017 · 1 comment
Closed

Frequently leaves behind bad routes causing unreachable host #421

khazhyk opened this issue Dec 20, 2017 · 1 comment

Comments

@khazhyk
Copy link

khazhyk commented Dec 20, 2017

I frequently have an issue where tunnelblick leaves around a bad route, causing it so I cannot connect to VPN or to the host at all due to unreachable error. I need to run route -n delete <host> to fix this issue.

I'm using Tunnelblick 3.7.4a (build 4920), but this has been happening for a while.

OSX 10.10.5

@jkbullard
Copy link
Contributor

This is usually due to an OpenVPN misconfiguration.

For example, including "user nobody" and "group nogroup" in a configuration that relies on OpenVPN doing the routing (as yours apparently does). The problem is that with "user nobody", OpenVPN is running as "nobody" when the disconnect occurs, and "nobody" does not have the permissions needed to restore the routes. (Without "user nobody", OpenVPN continues running as "root", so when the disconnect occurs, OpenVPN can restore the routes.

You can solve that problem by removing "user nobody" and "group nogroup" from the OpenVPN configuration file. (A computer administrator must do this.)

Another solution that usually works, and which can be done by a non-computer-administrator, is to have Tunnelblick reset the primary interface when there is a disconnect:

  • In older versions of Tunnelblick (prior to 3.7.5beta03), use the "Reset the primary interface after disconnecting" checkbox on the "Settings" tab on the "Configurations" panel of Tunnelblick's "VPN Details" window.

  • On newer versions of Tunnelblick, 3.7.5beta03 and higher), set both the "On expected disconnect" and the "On unexpected disconnect" settings to "Reset Primary Interface". They are on the "Settings" tab on the "Configurations" panel of Tunnelblick's "VPN Details" window.

Note that when making a change to almost any Tunnelblick setting, the change will be applied to all configurations that are selected in the list on the left side of the "Configurations" panel, so you can change the settings for multiple configurations at one time.

If trying these solutions doesn't fix the problem you are having, please post to the Tunnelblick Discussion Group and include the "diagnostic info" described in Read Before You Post. If the discussion group is blocked, post here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants