# Routing traffic in Meshnet
## Introduction
Meshnet's traffic routing feature allows you to use another device's public IP address for your internet connection, essentially turning that device into a VPN server. With a single click, you can obtain either your home IP address or the IP address associated with your [own VPN server](https://meshnet.nordvpn.com/how-to/traffic-routing). Additionally, while routing traffic, you can seamlessly connect to a remote [local area network](https://nordvpn.com/blog/what-is-lan/) (LAN) and manage other devices as if you were physically present on the same network.
To familiarize yourself with the traffic routing functionality, have a look at this video:
{% embed url="" %}
Alternatively, the written instructions below cover the availability and functionality of the traffic routing feature and detail its usage on available systems.
## How traffic routing works
When you choose to route traffic through a Meshnet peer, the selected [*host*](#user-content-fn-1)[^1] device acts as a VPN server. Your device, which acts as the [*client*](#user-content-fn-2)[^2], is assigned the public IP address of the host and connects to the internet using it instead of your standard IP address. This functionality allows you to protect your connection and obtain a known, specific IP address.
Figure 1. Traffic routing flow
To visualize this process, consider the following example illustrated in the diagram:
1. A phone (client) has a public IP of `185.61.156.14`.
2. Then, it routes traffic through the home computer (host) with a public IP of `45.92.11.187`.
3. As a result, the phone (client) accesses the internet using the same public IP address as the home computer (host), `45.92.11.187`.
{% hint style="info" %}
**Note**
The traffic routing connection automatically uses the same NordVPN DNS addresses (`103.86.96.100` and `103.86.99.100`) as a standard VPN connection. They are used for efficient query processing and to prevent [DNS leaks](https://nordvpn.com/dns-leak-test/).
{% endhint %}
### Local network access possibilities
With [local network permissions](https://meshnet.nordvpn.com/features/explaining-permissions/local-network-permissions) granted, traffic routing allows you to establish connections with other devices within the host's LAN. You can interact with the devices on the remote LAN using their original IP addresses. This networking configuration empowers you to remotely manage a variety of appliances that would otherwise be inaccessible, such as [IP cameras](https://meshnet.nordvpn.com/how-to/remote-access/access-ip-camera) and [network-attached storage](https://meshnet.nordvpn.com/how-to/remote-access/access-nas) (NAS).
Figure 2. Routing traffic with the Local network permission enabled
Using the model above as an example, while routing traffic from your laptop through the home computer, you can access the local web server using its LAN IP address, as shown:
## Feature availability and device compatibility
The traffic routing feature is available on all devices compatible with Meshnet. However, due to technical constraints, only certain devices can serve as hosts.
The table below acts as a reference point to check whether your device can act as a traffic routing host or only as a client.
| Host devices | Client devices |
| ------------------------------------------------------------------------- | ------------------------------------------- |
| Windows | Windows |
| macOS ([direct download](https://nordvpn.com/download/mac/) version only) | Android (including ChromeOS) |
| Linux | iOS |
| | macOS |
| | Linux |
| | Android TV (including FireOS and Google TV) |
{% hint style="info" %}
**Note**
The App Store version of the macOS NordVPN app doesn't provide the required functionality for your device to act as a traffic routing host.
{% endhint %}
## Traffic routing caveats
Even though traffic routing opens a multitude of opportunities, it is vital to be aware of the potential situations that could arise while using this feature. When using traffic routing, be cautious that:
* A client device is assigned your [public IP address](https://nordvpn.com/what-is-my-ip/), which potentially could lead to illegal activities being performed under your IP.
* A client device, with the [Local network permissions](https://meshnet.nordvpn.com/features/explaining-permissions/local-network-permissions) enabled, could access other devices on your LAN and make unauthorized changes.
* A host device could monitor your network activity, such as [DNS queries](https://nordvpn.com/cybersecurity/glossary/dns-query/).
## See also
* For guidance on using traffic routing across different platforms, refer to these articles:
* [Using traffic routing on Windows](https://meshnet.nordvpn.com/features/routing-traffic-in-meshnet/traffic-routing-windows)
* [Using traffic routing on Android](https://meshnet.nordvpn.com/features/routing-traffic-in-meshnet/traffic-routing-android)
* [Using traffic routing on iPhone/iPad](https://meshnet.nordvpn.com/features/routing-traffic-in-meshnet/traffic-routing-ios)
* [Using traffic routing on macOS](https://meshnet.nordvpn.com/features/routing-traffic-in-meshnet/traffic-routing-macos)
* [Using traffic routing on Linux](https://meshnet.nordvpn.com/features/routing-traffic-in-meshnet/traffic-routing-linux)
* [Using traffic routing on Android TV](https://meshnet.nordvpn.com/features/routing-traffic-in-meshnet/traffic-routing-androidtv)
* For information on setting up a personal VPN server using traffic routing, explore our how-to guides in the [Own VPN server setup](https://meshnet.nordvpn.com/how-to/traffic-routing) section.
[^1]: Host devices are devices that can act as a VPN server and allow you to route traffic through them.
[^2]: Client devices are devices that can use the traffic routing feature to route their connection through a host device.
