split-tunnel-vpn.com A guide by Firezone

Split tunnel VPN or full tunnel VPN

A split tunnel VPN sends only the traffic for your private networks through the tunnel. A full tunnel VPN sends all traffic through it. This guide explains the two designs, the trade-offs, and the mistakes that break a split.

See the Firezone full tunnelBook a demo

How a split tunnel VPN selects a path for each packetAn app on a laptop sends a packet. The route table on the laptop compares the destination with its routes. A packet that matches a tunnel route goes through the tunnel to a VPN gateway, which forwards it to a private app or a database. A packet that matches no tunnel route goes to the local router and then directly to a public website.LaptopDirect pathPrivate networkpacketno matchdirectmatchforwardAppsends a packetRoute tableselects a pathPublic websitesees your own IPLocal routerhome or Wi-FiVPN gatewayend of the tunnelPrivate app10.20.0.15Database10.20.30.40
  1. The route table decides

    The operating system compares the destination of each packet with its list of routes.

  2. Private traffic enters the tunnel

    A destination that matches a tunnel route goes to the VPN gateway in encrypted form.

  3. The gateway forwards it

    The VPN gateway removes the encryption and sends the packet to the private host.

  4. All other traffic goes direct

    A destination that matches no tunnel route uses the local network. A full tunnel removes this path.

What split tunnel and full tunnel mean

A VPN client adds routes to the device. The routes decide which packets enter the tunnel. The two designs differ only in those routes.

  • Full tunnel VPN. The client replaces the default route. All traffic goes through the tunnel, and the VPN gateway sends internet traffic out from the company network.
  • Split tunnel VPN. The client adds routes for the private networks only, for example 10.0.0.0/8. All other traffic uses the local network of the device.

The name "split tunneling" describes the result. The traffic of one device splits into two paths at the route table.

Inverse split tunneling

Inverse split tunneling starts with a full tunnel and then removes some destinations from it. Teams use it to keep video calls or large updates off the tunnel. The excluded traffic goes direct, and all other traffic stays inside.

The trade-offs between the two designs

Neither design is correct for every team. Each one moves a cost to a different place.

Speed and bandwidth cost

A full tunnel sends each video stream and each download through the company network. The traffic makes a longer trip, and the company pays for the bandwidth two times, once in and once out. A split tunnel keeps that traffic on the direct path.

Privacy and visibility

With a full tunnel, the company can inspect and log the internet traffic of each device. That visibility helps the security team, and some compliance rules require it. It also means that the company carries the personal traffic of each remote worker.

Security on public Wi-Fi

On public Wi-Fi, other people share the local network with you. A full tunnel encrypts each packet before it leaves the device, so the local network sees only the tunnel. A split tunnel protects only the private traffic. The other traffic relies on its own encryption, such as HTTPS.

Failure effects

If a full tunnel stops, the device loses all network access. If a split tunnel stops, the device loses only the private networks.

How the route table selects a path

The operating system uses the longest prefix match rule. When two routes contain the destination address, the route with the longer prefix wins. A /24 route beats a /16 route, and a /32 route beats all other routes.

The default route, 0.0.0.0/0, has the shortest prefix possible. It matches every address, so it wins only when no other route matches. A full tunnel VPN changes the default route. A split tunnel VPN leaves it alone.

This rule makes inverse split tunneling possible. The tunnel owns the default route, and a more specific route sends the excluded destinations to the local network.

Try the routes

These rules show a split tunnel with four routes, written as Firezone Resources. Type an IPv4 address to see which rule matches. When more than one rule contains the address, the longest prefix wins.

RouteWhere the packet goes
10.0.0.0/8Through the tunnel to the Gateway in the data center Site
10.20.0.0/16Through the tunnel to the Gateway in the production Site
10.20.30.40/32Through the tunnel to the database host, for the database team only
192.168.50.0/24Through the tunnel to the Gateway in the office Site
All other addressesOn the direct internet path, outside the tunnel

The usual split tunnel mistakes

A split tunnel has more parts than a full tunnel, so it has more ways to fail. Three mistakes cause most of the problems.

Overlapping routes

Many home routers use 192.168.1.0/24, and many offices use the same range. When the tunnel route and the local network overlap, the device cannot tell the home printer from the office server. Use address ranges for company networks that home routers do not use.

DNS that does not follow the split

The routes send packets for 10.20.0.15 into the tunnel, but the user types a name. If the query for that name goes to a public resolver, the user gets no answer. The private name also leaks to that resolver. Send the queries for private names to a resolver inside the private network.

Routes that are too wide

A route for 10.0.0.0/8 is easy to write. It also puts every host in that range one hop away from each remote device. A route gives reach, and it is not an access rule. Add a rule for each service that says who can connect.

A checklist

  1. Write down each private range and make sure that no two ranges overlap.
  2. Send private names to an internal resolver, and test for leaks from a home network.
  3. Decide if internet traffic needs the tunnel on public Wi-Fi.
  4. Replace each wide route with narrow rules as you learn what people use.

How Firezone does split tunnel and full tunnel

In Firezone, split tunneling is always on. You do not write routes. You add Resources, and only the traffic for those Resources goes through Firezone.

  • The split is defined for each Resource. A Resource is a DNS name, an IP address, or a CIDR range. A Policy gives one Group access to one Resource, and access is default-deny.
  • The most specific Resource wins. Firezone uses the longest prefix for CIDR Resources, and an IP Resource beats any CIDR Resource.
  • DNS follows the split. The Client resolves a name that matches a DNS Resource on the Gateway, with the resolver of that network. All other names use the resolver that you select.
  • Each Resource can be narrow. Traffic restrictions limit a Resource to protocols and port ranges, for example TCP port 22 only.

A full tunnel when you want one

The Internet Resource adds a full tunnel. It routes 0.0.0.0/0 and ::/0 through Gateways that you run in a special Internet Site. The Client uses the nearest healthy Gateway.

Private Resources keep their own path, because a more specific Resource always takes priority over the Internet Resource. Users can turn the Internet Resource off in the Client if it causes a problem. The Internet Resource is available on the Team plan and up.

Full tunnel VPN, split tunnel VPN, and Firezone

A legacy VPN makes you select one design for each tunnel. Firezone starts with a split and lets you add a full tunnel for the groups that need it.

Full tunnel VPNSplit tunnel VPNFirezone
What goes through the tunnelAll trafficThe routes that you listThe Resources of each user, and the internet if you add the Internet Resource
Internet traffic takes the direct pathNoYesYesUnless you add the Internet Resource
Internet traffic is encrypted on public Wi-FiYesNoOnly private traffic uses the tunnelPartialWith the Internet Resource
Company visibility of internet trafficYesNoPartialWith the Internet Resource
DNS follows the splitYesAll queries go insidePartialNeeds a separate split DNS setupYesDNS Resources resolve on the Gateway
An access rule for each serviceNoUsually a full networkPartialRoutes limit reach onlyYesOne Policy for each Resource
Rule for overlapping routesOne default routeLongest prefix, which you set by handThe most specific Resource wins

The table describes the usual design of each category. A specific product can be different. Read the documentation of the product before you decide.

Common questions

Is a split tunnel VPN less secure than a full tunnel VPN?

It depends on the risk. A split tunnel protects private traffic the same as a full tunnel. It does not protect or inspect internet traffic, which matters on public Wi-Fi. A full tunnel covers that traffic, but it gives each device a path to more of the network unless you add access rules.

Does split tunneling make the internet faster?

Usually, yes. Internet traffic goes direct and does not make a trip through the company network. Video calls and downloads get the most benefit. The private traffic has the same speed in the two designs.

What is inverse split tunneling?

Inverse split tunneling sends all traffic through the tunnel, with a list of exceptions that go direct. A normal split tunnel does the opposite. It sends only a list of destinations through the tunnel.

Why do private names fail when the split tunnel is connected?

The DNS query probably goes to a public resolver, which does not know your private names. The routes are correct, but DNS does not follow the split. Send the queries for your private domains to a resolver inside the private network.

Can I use split tunnel and full tunnel at the same time?

Yes, in Firezone. Private Resources always use the split, and each one goes to the Gateway in its own Site. If a Policy gives a Group the Internet Resource, the other traffic of those users goes through a Gateway in the Internet Site.

Start with a split, and add a full tunnel later

Firezone is zero trust access built on WireGuard. Each Resource has its own path and its own Policy, and the Internet Resource covers all other traffic when you need it. The Starter plan is free.

See plans and pricingBook a demo