A cybersecurity network diagram connects laptops, a smartphone, servers, and cloud storage through encrypted data flows.
VPN split tunneling is not one universal switch. NordVPN uses application rules on Windows and Android, but its Linux Allowlist operates on ports and subnets—a distinction that changes both setup and security exposure. Traffic excluded from the VPN does not receive that tunnel’s protection, and Linux exceptions also bypass NordVPN’s kill switch.

The useful question is not simply “Is split tunneling enabled?” It is “Which traffic takes which route—and what happens when that route fails?”

A cybersecurity network diagram connects laptops, a smartphone, servers, and cloud storage through encrypted data flows. Before changing your routing​

For the NordVPN procedures below, have the app installed and a working VPN connection before adding exceptions. Treat these as client-specific instructions, not settings shared by every VPN application.

Decide what you want to accomplish first: exclude one application, reach a local network destination, or implement an organization-wide routing policy. Those are different jobs. NordVPN’s app controls, OpenWrt router policies, and administrator-managed Windows VPN profiles act at different layers.

On a managed work device, ask IT before changing routing. Microsoft’s enterprise approach uses centrally configured destination exclusions, rather than asking employees to improvise application exceptions.

NordVPN setup on Windows, Android, and Linux​

Windows 10 and Windows 11​

NordVPN documents this sequence:

  1. Open the app’s Settings.
  2. Select Split tunneling and enable it.
  3. Choose Add apps.
  4. Select an application and click Add selected.

The list shows currently open applications; use Browse apps for another installed program. Check the rule’s routing mode before adding it.

Android​

Open Profile → Settings → VPN connection → Split tunneling. Enable the switch, then select applications to exclude from the VPN connection.

Linux​

Open Settings → Security and privacy → Allowlist, or use the CLI. Rules target ports, port ranges, or subnets—not individual applications. They apply in both directions, and matching traffic bypasses the tunnel and kill switch. There is no outbound-only option within this feature.

For example, NordVPN documents this TCP-port exception and its corresponding removal:

Code:
nordvpn allowlist add port 22 protocol TCP
nordvpn allowlist remove port 22 protocol TCP

Use a port exception only when needed; it is not an application-specific permission.

Test the exception, not just the connection​

A practical validation plan should check both sides of the split:

  • Confirm that the intended excluded application or destination works.
  • Confirm that traffic intended to remain tunneled still follows the VPN route.
  • Remove the exception and repeat the test to establish whether it actually caused the change.
  • Separately check behavior when the VPN disconnects.

These are recommended validation steps, not results from firsthand testing. They matter because routing and blocking are separate controls: an exception can be configured correctly yet still encounter a kill-switch restriction. NordVPN’s separate support guidance explicitly describes conflicts between split tunneling and its Internet Kill Switch.

Do not assume Linux’s Allowlist behavior applies to Windows or Android. NordVPN documents the Linux kill-switch bypass separately, while its Internet Kill Switch guidance warns that excluded apps can lose connectivity when both features are enabled. Disabling protection merely to make an app connect changes the security trade-off; it is not a neutral troubleshooting step.

Troubleshooting: save the network reset for last​

NordVPN identifies a possible DNS/IP mismatch: an excluded application may use the internet provider’s public IP while DNS still uses NordVPN’s servers, confusing some services’ location checks. That is a possible cause, not a diagnosis of every failed connection.

Start with reversible changes. Restart the device, check for another active VPN service, and consider resetting or reinstalling NordVPN. The company lists these among its troubleshooting options. Change one thing at a time so you can identify what helped.

A network reset is more disruptive. NordVPN warns that it resets saved Wi-Fi networks and passwords, VPN settings, and APN settings. Record the information needed to restore connectivity before proceeding, particularly on a remotely administered computer.

NordVPN’s documented desktop diagnostics sequence is:

  1. Select the question-mark button in the app’s lower-left corner.
  2. Choose Run diagnostics.
  3. Optionally include the offered diagnostic data, then select Continue.
  4. Choose Reset network.
  5. Wait for completion and restart the computer.

This is NordVPN’s diagnostics workflow, not a universal reset procedure for Windows, Android, and Linux.

Windows’ built-in VPN uses a different model​

Microsoft documents a force tunneling with exclusions approach for the built-in Windows VPN client on Windows 10 and Windows 11. Defined destination IP prefixes use the physical internet-connected interface, while other traffic continues through the VPN.

Administrators configure this through VPN profiles using the VPNv2 configuration service provider and ProfileXML; Microsoft identifies Intune as a typical distribution method. That is materially different from selecting an executable in NordVPN’s interface.

For Microsoft 365, Microsoft recommends focusing exceptions on published Optimize endpoint IP ranges. It estimates that these endpoints represent approximately 70–80% of traffic volume to Microsoft 365, not 70–80% of a user’s entire internet connection. Microsoft also cautions against using Microsoft 365 domain names as the basis for this split-tunnel configuration.

The practical lesson: excluding a whole productivity application is not equivalent to routing a defined set of service destinations directly.

Group policies and router-level alternatives​

OpenVPN Access Server provides another administrative model. Its version 3 documentation describes global full- or split-tunnel settings with user and group overrides. In its split-tunnel model, specified private subnets use the VPN while other traffic uses the client’s local internet connection. DNS handling can also differ between override configurations.

At home, OpenWrt’s Policy-Based Routing can select VPN or WAN routes for particular hosts, subnets, or domains. Its routing mechanisms can also match parameters such as source and destination addresses or interfaces. These policies belong on the router, not in an application picker.

Dev Odyssey’s OpenWrt walkthrough demonstrates creating and testing custom PBR policies. It is an example of that router-level approach, not a substitute for platform-specific NordVPN instructions.

The bottom line: choose the narrowest exception that accomplishes the task, test both tunneled and bypassed traffic, and understand the failure behavior. A green VPN status indicator is useful—but it is not a map of every connection leaving your device.

 

References

  1. VPN Split Tunneling Setup on Windows, Android, Linux - NeoTeo NeoTeo 2026-10-25T01:38:26+00:00
  2. How Kill Switch and Split Tunneling interact in NordVPN? – Live Chat, VPN Setup, Troubleshooting | NordVPN Customer Support support.nordvpn.com
  3. What is Split Tunneling and how to use it with NordVPN? – Live Chat, VPN Setup, Troubleshooting | NordVPN Customer Support support.nordvpn.com