# Network Mapping

Sometimes remote networks routed through the VPN server can overlap or conflict with the local network of the remote user connecting. This can cause connection issues and prevent the user from accessing network resources. Network mapping allows remapping a route on the server to a different subnet of the same size. In the diagram below the VPC network `192.168.0.0/16` overlaps with the users network `192.168.1.0/24`. This will be fixed by mapping `192.168.0.0/16` to `10.168.0.0/16`. The remote user will then be able to access all hosts on `192.168.0.0/16` using the subnet `10.168.0.0/16` without effecting connection to resources on the local network.

![](/files/BBL7sSBlLcw1kCQz6LSF)

### Configure Server

When adding or modifying a route on the server enter the original network in the route *Network* field. Then enter the new subnet that will be used to access this network in the *NAT Network Mapping* field. This configuration will require NAT and doesn't support non-NAT configurations.

![](/files/3GwVjJ7CtEvYxW4ZpXqB)

Once done the route will have a label *NAT Mapped* and will be ready to use.

![](/files/bqX8hbu1pNdKoh8Wf4M5)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pritunl.com/kb/vpn/servers/network-mapping.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.