Routing traffic from Windows

Learn how to handle Meshnet's traffic routing feature on Windows.

Before you begin

To start using traffic routing, make sure that the device you want to route traffic through meets the following criteria:

• The NordVPN app is running, and the Meshnet feature is enabled in the app.

• The device is connected to your Meshnet.

• The Traffic routing through your device permission is granted for your client device. To learn more, see Traffic routing permissions.

Note

You can add devices to your Meshnet in two ways, depending on device ownership:

• To add your own device, just enable Meshnet on that device. See Using Meshnet on Windows for details.

• To add an external device, send an invitation via the NordVPN app with the owner's email. Ensure the invitation is accepted. See Adding external Meshnet devices on Windows.

Start routing traffic

To start a traffic routing connection on Windows, follow these steps:

1. Open NordVPN and select Dashboard.

2. Under the search field, select the Devices tab.

3. Click the device that you want to route traffic through.

   

Once connected, you will see the host device’s details on the Dashboard tab.

Tip

If you see "No permission" under the desired device, ensure that the peer device has granted your device the traffic routing permissions.

Note

When routing traffic for the first time, you will receive a prompt detailing the caveats of traffic routing. Read this information and click Continue to proceed with the connection.

Tip

You can utilize your preferred DNS addresses for the traffic routing connection by using the app's Custom DNS feature. The DNS servers can be entered in NordVPN's Settings > Connection and security > Use custom DNS dropdown menu.

An example of how to use the custom DNS functionality is available in the How to set up your network protection with Pi-hole article.

Stop routing traffic

To terminate the traffic routing connection, click the Disconnect button on the Dashboard tab.

Note

Connection pause is currently not available while routing traffic through a Meshnet peer device.