> For the complete documentation index, see [llms.txt](https://meshnet.nordvpn.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://meshnet.nordvpn.com/features/routing-traffic-in-meshnet/traffic-routing-android.md).
# Routing traffic from Android
Learn how to handle Meshnet's traffic routing feature on Android.
## 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](/features/explaining-permissions/traffic-routing-permissions.md).
{% hint style="info" %}
**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 Android](/getting-started/how-to-start-using-meshnet/using-meshnet-on-android.md#add-your-own-devices) 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 Android](/features/linking-devices-in-meshnet/adding-external-meshnet-devices-on-android.md).
{% endhint %}
## Start routing traffic
To start routing traffic from your Android device, follow these steps:
1. Open **NordVPN.**
2. Do one of the following:
1. At the top of the screen, tap **Search all locations**.
2. Under the map, tap **All locations >**.
3. Select the **Meshnet** tab.
4. If Meshnet is disabled, tap **Turn on Meshnet** to enable the feature.
5. Locate the device that you want to route traffic through and tap it.
{% hint style="success" %}
**Tip**
If you see "No permission" under the desired device, ensure that the peer device has granted your device the [traffic routing permissions](/features/explaining-permissions/traffic-routing-permissions.md#changing-permissions).
{% endhint %}
Upon establishing the connection, you will see the host device’s Nord name on the **Home** page.
{% hint style="success" %}
**Tip**
You can use the NordVPN [What is my IP](https://nordvpn.com/what-is-my-ip/) website to confirm that your public IP has changed. The newly assigned IP address should be the same as the traffic routing host device's.
{% endhint %}
## Stop routing traffic
To stop traffic routing, you can use the following methods:
* Tap the **Disconnect** button on the **Home** page.
* Tap the host device again in the **Meshnet** tab of search.
{% hint style="info" %}
**Note**
Connection pause is currently not available while routing traffic through a Meshnet peer device.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://meshnet.nordvpn.com/features/routing-traffic-in-meshnet/traffic-routing-android.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
