Get One Month of Starlink FreeSPECIAL OFFER: GET A FREE MONTH OF STARLINK >
Wireless router and cable representing Starlink hardware and accessories

How to Use Split-Tunnel VPN With Starlink Without Losing Local Access

Tips & Tricks

Back to Tips & Tricks

Split-tunnel VPN is useful on Starlink when you want private work or home-lab traffic to use a VPN, while ordinary browsing and local devices continue to use the normal Starlink connection. The exact setting names differ between VPN apps and routers, but the planning and test sequence is the same.

What split tunneling changes

A full-tunnel VPN sends nearly all traffic through the VPN provider or remote network. A split tunnel sends only selected traffic through it.

That distinction matters on Starlink because:

  • Local printers, cameras, NAS devices and router pages usually need to stay reachable on the local network.
  • A full tunnel can add latency or reduce speed for traffic that does not need privacy or remote access.
  • Work systems may require a private address or company DNS, while personal browsing should stay outside the work tunnel.
  • Split tunneling does not remove Starlink CGNAT or create inbound access by itself.

There are two common policies:

  1. Include only these destinations: send named work subnets, private services or selected applications through the VPN.
  2. Exclude these destinations: send normal traffic through the VPN, but keep local networks and selected services outside it.

Use the first policy when you know the private networks that need the tunnel. Use the second only when the VPN software has reliable local-network exclusions and you have tested them.

Plan the traffic before changing settings

Write down four small lists:

  • Private destinations: work subnets, a home server network, or a service that is reachable only through the VPN.
  • Local destinations: the Starlink router, a third-party router, printers, cameras, NAS devices and smart-home controllers.
  • Direct destinations: everyday websites, streaming services, software updates and anything that does not need the tunnel.
  • Recovery path: a second device, a wired connection or the VPN app's disable switch.

If you do not know a private destination's address, ask the network administrator or inspect a working connection before changing the Starlink network. Do not guess a broad route such as an entire private address range if it could capture devices that should remain local.

Choose where to configure it

Device-level VPN

A VPN app on one laptop or phone is the easiest place to start. Enable split tunneling, then choose either applications, domains or destination networks if the app supports them.

Keep local-network access enabled while testing. Some apps call this Allow LAN traffic, Bypass local networks or Local network sharing. It is not the same as disabling the VPN.

Start with one device and one private destination. This keeps a mistaken route from affecting the whole Starlink household.

Router-level policy routing

A router or firewall can send selected devices or destination subnets through the VPN. This is useful when several devices need the same policy, but it needs more care.

Before applying a router policy, identify:

  • Which interface is the normal Starlink route.
  • Which interface is the VPN route.
  • Which LAN subnets must remain local.
  • Which DNS server each route should use.
  • Whether the router's kill switch blocks local traffic when the VPN drops.

Avoid sending the router's own management address through a remote tunnel unless you have a tested recovery method. Keep at least one wired or trusted local path available while applying the rule.

Overlay networks and exit nodes

Tools such as mesh VPNs can provide private subnet access or an exit node. These are different functions:

  • A subnet route reaches selected private networks.
  • An exit node sends ordinary internet traffic through another device.

If you only need access to a home NAS or work subnet, use a route to that network rather than making every device use an exit node. Confirm that the device is authorised to advertise or accept the route, and do not expose a private subnet more broadly than necessary.

A safe setup sequence

  1. Record the current Starlink status, public IP result, local router address and one normal speed test. Treat these as comparison points, not promises of a particular performance level.
  2. Configure the VPN on one test device only.
  3. Start with a narrow rule for one private destination or one application.
  4. Keep local-network access enabled and leave the Starlink app or router page outside the tunnel while testing.
  5. Reconnect the VPN and verify the private destination.
  6. Test a local device such as a printer or NAS.
  7. Open an ordinary website and check that it still works when the VPN is connected and disconnected.
  8. Repeat the checks after the VPN reconnects, the device wakes from sleep and the Starlink router restarts.
  9. Only then expand the rule to more devices, destinations or applications.

If the VPN client offers a kill switch, test both states. A strict kill switch may correctly stop traffic when the VPN drops, but it can also make local devices appear offline if local access is not explicitly allowed.

Check DNS and IPv6 separately

Routing and name resolution can disagree. A private hostname may fail even when its private IP address works because the device is using the wrong DNS server. Conversely, a public hostname may resolve through a VPN resolver while the connection itself goes directly through Starlink.

Test both:

  • The private service by hostname, if one exists.
  • The same service by its approved private address.
  • A normal public website.
  • A local device by its local name and address.

If IPv6 is enabled, repeat the tests with IPv6 in mind. A policy that handles IPv4 only may allow an application to use a different path over IPv6. Do not assume that an IPv4 split-tunnel rule protects IPv6 traffic. Either configure IPv6 rules, disable it only where appropriate for the network's policy, or confirm with the VPN provider and administrator how IPv6 is handled.

Troubleshooting checklist

The private service is unreachable

  • Confirm the VPN is connected.
  • Check that the destination route is present and specific enough.
  • Try the approved private address instead of the hostname.
  • Check whether the remote network overlaps your local Starlink LAN range.
  • Ask whether the service requires company DNS or another authentication step.

The internet is slow only while the VPN is connected

  • Check whether the rule accidentally became a full tunnel.
  • Test one direct website and one private destination separately.
  • Look for a distant VPN endpoint or an overloaded gateway.
  • Check whether a router policy is sending large updates or streaming through the tunnel.

The printer, NAS or router page disappears

  • Enable the VPN app's local-network access option.
  • Make sure the local subnet is excluded from the tunnel.
  • Check whether the VPN kill switch blocks local traffic.
  • If the device is managed by a router policy, confirm the local route is more specific than the default VPN route.

The rule works until the Starlink router restarts

  • Check whether the router recreated its routes in a different order.
  • Confirm the VPN interface is available before policy rules are applied.
  • Save a recovery procedure and test it after a controlled restart.
  • Keep one device outside the policy while you make changes.

Final verification matrix

Before treating the setup as complete, record the result for each combination:

  • VPN disconnected: local device, private destination, public website.
  • VPN connected: local device, private destination, public website.
  • VPN temporarily unavailable: local device and public website.
  • After sleep or restart: the same three checks.
  • IPv4 and IPv6: repeat the private and public checks if both are enabled.

A good split-tunnel setup has an intentional answer for every path. Private traffic uses the VPN, local traffic stays local, direct traffic uses the normal Starlink route, and a failure leaves you with a known recovery path rather than a locked-out network.