Insights
WireGuard split tunnel: route only the destinations you need
Configure WireGuard split tunneling with AllowedIPs, then check Linux routes, DNS and service access. Learn IPv6 and per-app limits.

On this page
WireGuard split tunneling sends traffic for selected Internet Protocol (IP) addresses or address ranges through the tunnel. Other traffic uses your normal connection when your client's routing setup allows it.
In short:
- Selected destinations.
AllowedIPslists the remote addresses or subnets you want through WireGuard. - Other traffic stays direct. Unselected destinations use your normal connection when routing allows it.
- Names and apps differ. Name lookups and per-app routing need separate attention.
Choose what goes through the tunnel
In your client's [Peer] section, AllowedIPs selects the peer for outgoing destinationsOpens in a new tab and limits which source addresses WireGuard accepts from that peer. A peer is another WireGuard device. For a split tunnel, list only the remote addresses or subnets, meaning address ranges, you need.
The catch-all entries 0.0.0.0/0 and ::/0 request full-tunnel routing for Internet Protocol version 4 (IPv4) and version 6 (IPv6), respectively. Clients and tools such as wg-quick normally create operating-system routes from the profile, but AllowedIPs isn't a universal route-installation command. Traffic sent directly isn't carried by WireGuard, though application encryption may still protect its content.
Set the remote destinations you need
Edit only a device you own or administer. Save the original profileOpens in a new tab, and keep another way to reach the device if you're changing a remote connection.
1. Get the approved remote ranges.
Use the exact addresses or subnets supplied for your remote services. Don't assume the example networks below match your network.
2. Replace the existing client's destination list.
Change the existing AllowedIPs entry in [Peer] instead of adding a duplicate setting. Preserve the existing keys, endpoint and unrelated settings.
This hypothetical fragment assumes your remote services use the two listed networks. It's not a complete or tested profile, so replace both networks with your approved ranges.
[Peer]
AllowedIPs = 10.0.0.0/24, 192.168.100.0/24
3. Save and reactivate through the same client or manager.
Changing the client doesn't enable gateway forwarding, grant service access or create a return route. Don't copy the client's remote destination list into the server's peer entry.
4. Check all three results.
Your intended remote destination should select the WireGuard interface. An unrelated public destination should select your ordinary connection, and the intended remote service should work. Use the Linux checks below where applicable.
Decide where DNS lookups go
Domain Name System (DNS) turns service names into IP addresses. Choosing a resolver, the server that answers those lookups, is separate from routing service traffic. A tunnel DNS setting can affect public-name lookups too.
Domain-based split DNS can send internal-name queries to a private resolver while other queries use your normal resolver. It's an extra resolver setup, not an automatic property of AllowedIPs. The private resolver must be reachable through the intended route. On Linux, systemd-resolved must be installed, running and integrated with your active network manager before you use its domain-routing settings.
Include IPv6 in your routing plan
IPv4 entries don't cover IPv6 destinations. If your remote services use IPv6 and the tunnel supports it, add their approved IPv6 prefixes to AllowedIPs too. Leaving unrelated IPv6 traffic direct can be intentional in a split tunnel. Check that it matches your plan instead of treating every direct IPv6 flow as a leak or disabling IPv6 by default.
Check whether you need per-app routing
AllowedIPs selects destinations, not application names. A browser and another app reaching the same IP address aren't separated by that setting alone.
Some Android clients add app selection and exclusion controls. Check your specific client's current documentation before using those controls. Don't assume one client's interface labels or app controls apply to every Android variant, Windows or iOS.
Check the route before changing more settings
On Linux, run these checks only on a device you own or administer. These inspection commands don't edit your profile. Replace wg0 with your WireGuard interface and 192.168.100.50 with an approved remote destination.
1. Inspect the active peer's destination list.
sudo wg show wg0 allowed-ips
You should see a listed range that contains your remote address. That proves the active peer includes that destination, not that the service can answer. If it's missing, check that you edited and reactivated the intended profile.
2. Check the remote route.
ip route get 192.168.100.50
You should see dev wg0, using your interface's name. This shows the selected route for that lookup, not successful delivery. If another interface appears, inspect routing and any overlapping local and remote ranges before changing DNS.
3. Check an unrelated public route.
ip route get 8.8.8.8
Assuming this example address is outside your approved ranges, the result should select your ordinary connection. If it selects WireGuard, look for remaining catch-all routes or policy rules. Repeat the route checks for relevant IPv6 destinations if your plan uses IPv6.
4. Inspect policy routing when results differ.
ip rule
ip route show table all
Policy routing uses rules to choose which routing table handles traffic. Under Linux wg-quick full-tunnel policyOpens in a new tab, traffic without a specific route follows custom default-routing rules. Specific routes can preserve direct access, so the main routing table alone may not explain the result. Use these outputs to check the rules and tables before editing more settings.
5. Test the intended service by IP, then by name.
Use a service that supports access by IP for this comparison. If it works by IP but fails by name, check name resolution and the resolver's route. That points toward DNS checks, but doesn't prove DNS is the only problem. If the route uses WireGuard but the service fails by IP, check peer connectivity, gateway forwarding, firewall policy and the remote system's return route.
An unchanged public IP or a traceroute alone doesn't prove that all intended traffic follows your plan.
Where doxx.net fits. doxx.net is a private network for people and agents, run on its own IP space, DNS root and hardware. For private device access, create an account, download the appOpens in a new tab and connect a device or agent.