Tunnelblick All Traffic Through Vpn

Posted on  by



12) Open Tunnelblick by double-clicking on its icon (from the Applications folder). 13) Select the configuration you have added (left column), then click on 'Settings'. 14) In the settings window, check the box 'Route all IPv4 traffic through the VPN', then you can close the Tunnelblick window. This assumes, I only want to access resources from the VPN in the 192.168.2.XXX ip-range. But it still allows me to access the internet and all other resources (as the VPN in my example only allows access to certain resources, but not the internet). This also assumes, the VPN (in my case Tunnelblick) uses tap0 as the network adapter.

Force all traffic through OpenVPN connection

Through

This is a really quick one, as we use this trick a lot when working remotely, but we always have to scrabble around to find the info!

We use the open source OpenVPN for our office VPN. In general it’s great, however when working away from the office, it’s configured such that any request for a resource first checks outside of the firewall to see if it can access it. If it can, it does, no VPN involved. If it can’t, it then tries inside the VPN tunnel.

Tunnelblick All Traffic Through Vpn

For example, with the VPN connected, if I try to go to http://blog.sellorm.com, access occurs out side of the VPN as the resource is on the open internet. If I try to access something like http://rstudio.office.local, that isn’t on the open internet, access takes place through the VPN. This is a really great way of reducing traffic through the VPN to include only access to essential resources. We know this isn’t the most secure option, but it works for us for the moment.

There is one interesting exception to this however, and that is systems on public cloud providers like Amazon’s AWS. These systems are by necessity available on the public internet, but we generally use firewalls to only permit access from the office.

Unfortunately, this breaks the configuration above because as the hostname of the resource can be looked up on the open internet, the client thinks it should be able to access it outside of the VPN. As access is not permitted outside of the office though, this request will eventually fail. This means that we need to temporarily push all traffic through the VPN while we work with that AWS resource.

Vpn

As a Mac user, using the excellent TunnelBlick OpenVPN client, this is easy for me, as they helpfully provide a ‘Route all IPv4 traffic through the VPN’ tick box. For my Windows using colleagues however, it’s not quite so simple. They must edit their OpenVPN config file and manual add the following line to the end, before restarting their VPN connection.

This file is often just called client.ovpn.

Hopefully this quick post make this easier to find for me next time someone asks about it as well as helping someone else facing the same issue in the future.

Tunnelblick all traffic through vpn connection

Tunnelblick All Traffic Through Vpn Free

Highlighted Articles
News
Installing Tunnelblick
Uninstalling Tunnelblick
Setting up Configurations
Using Tunnelblick
Getting VPN Service
Common Problems
Configuring OpenVPN
Release Notes
Thanks
FAQ

Discussion Group
Read Before You Post

On This Page
If OpenVPN is connected to the server but you can't access the Internet
How to check your DNS settings
How to use a different DNS server
Use a different DNS server whether or not a VPN is active
Use a different DNS server only when the VPN is active
If OpenVPN is connected to the server but your IP address does not change
How to test your IP address

Troubleshooting this problem could be very simple: try connecting the VPN with and without 'Set nameserver' selected. If one way or the other solves your problem, you're done!

OpenVPN is such a powerful tool with so many options, and computer configurations are so varied, that it is impossible to have an exhaustive troubleshooting guide. This guide is meant for the most common setups, so if it doesn't apply to your situation, or doesn't help, see the Support page for guidance.

This page assumes that you are successfully connected to a VPN server. If not, or if you aren't sure, look at Common Problems.

If OpenVPN is connected to the server but you can't access the Internet

After connecting, if you can't reach the Internet, it's likely that your setup has

  • A DNS problem and/or
  • A routing problem and/or
  • A problem with the VPN server

Tunnelblick includes the ability to diagnose some DNS problems and will warn you about some common configuration problems.

Check for a DNS problem:
If OpenVPN connected to the server properly, but you are having trouble connecting to websites, the first thing to find out is if there is a DNS problem. To check that, try to access a website by using its IP address instead of its name. If the IP address works, but the name doesn't, there is a DNS problem. (Consider the IP address to be 'working' if any of the webpage loads.)

If you don't have a DNS problem then there is something else going on. See the Support page for guidance.

If you have a DNS problem:

  1. See if your network settings manually specify a DNS server. If they do, that server will be used even when the VPN is active unless you put a check in 'Allow changes to manually-set network settings' on Tunnelblick's 'Advanced' settings page. If the manual DNS server is your ISP's DNS server, it is probably set up to ignore queries that come from outside the network. When you are connected to the VPN, your queries come from the VPN server, which is probably outside the ISP's network, so the ISP's DNS server will ignore your request. You should set up your computer to use a free public DNS server (see How to use a different DNS server, below) while the VPN is active.

  2. If your DNS settings are specified by DHCP, check your DNS settings both before you connect to the VPN and while you are connected.
    • If the DNS settings are the same, try setting up your computer to use a free public DNS server (see How to use a different DNS server, below).
    • If the DNS settings are different, the VPN is using a DNS server specified by the VPN setup. Contact the person who maintains your VPN server to find out why that DNS server is not functioning properly.

How to check your DNS settings

  1. Launch System Preferences,
  2. Click 'Network'
    Your DNS server list is one of the entries on the right. It is a list of IP addresses, separated by commas. macOS will use the first one unless it fails to respond to requests, in which case it will try the second, then the third, etc.

Note: If the DNS server list is dimmed (grayed out), it was set via DHCP, not manually.

How to use a different DNS server

There are two ways to set up a different DNS server:

Use a different DNS server whether or not a VPN is active

You can set your computer up to use a different DNS server all the time. Google Public DNS is free, and OpenDNS has a free version. There are lots of others. To use such a DNS server all the time (whether or not a VPN is connected):

  1. Launch System Preferences,
  2. Click 'Network'
  3. Copy/paste the following '8.8.8.8,8.8.4.4,208.67.222.222,208.67.220.220' (without the quotation marks) into the box to the right of 'DNS Server'

This will set up your computer to always (whether or not you are connected to the VPN) use two Google DNS servers and two OpenDNS servers (in that order). Substitute the addresses for the DNS provider of your choice if you want.

Use a different DNS server only when the VPN is active

Note: This will only work if you specify 'Set nameserver' in Tunnelblick's settings for the configuration.

Add a line to your OpenVPN configuration file for each DNS server: 'dhcp-option DNSaddress' (substitute the DNS server's IP address for address). (To add two servers, add two lines to the OpenVPN configuration file, one for each server.)

If OpenVPN is connected to the server but your IP address does not change

If you have a check in the 'Check if the apparent public IP address changed after connecting' checkbox on the 'Settings' tab of Tunnelblick's 'VPN Details' window, and your IP address doesn't change after connecting, a window will pop up to notify you.

If OpenVPN connects to the server properly but your IP address does not change, your OpenVPN setup needs to include the '--redirect-gateway' option. By default, OpenVPN only sends some traffic through the VPN — traffic that is specifically destined for the VPN network itself. The '--redirect-gateway' option tells OpenVPN to send all IPv4 traffic through the VPN.

There are three ways the option can be added; you need only use one:

  • Put a check in the 'Route all Ipv4 traffic through the VPN' checkbox on the 'Settings' tab of Tunnelblick's 'VPN Details' window.
  • Add this: redirect-gateway def1 as a separate line in your client's OpenVPN configuration file.
  • Add this: push 'redirect-gateway def1' as a separate line in your server's OpenVPN configuration file.

(The '--' at the start of an OpenVPN option is omitted when the option appears in a configuration file.)

How to test your IP address

You can find out what IP address your computer is using by going to https://tunnelblick.net/ipinfo.

The first number shown is your apparent public IP address:

Note: tunnelblick.net does not use Javascript, other client-side scripting, plugins, trackers, beacons, or web bugs, and it does not carry advertising. It does not store cookies or any other data on your computer (except as noted in the tunnelblick.net privacy policy).

If you have checked 'Check if the apparent public IP address changed after connecting', the IP address will be displayed in the Tunnelblick menu while you are connected: