> For the complete documentation index, see [llms.txt](https://learn.netmaker.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.netmaker.io/help-articles/egress-route-conflict-with-local-network-route.md).

# Egress route conflict with local network route

A common issue when using Egress Routes is a conflict between the remote network route and the user’s local network route. This usually happens when both networks use the same private IP range.

For example:

| Network                                  | Subnet           |
| ---------------------------------------- | ---------------- |
| User’s local network                     | `192.168.1.0/24` |
| Remote network behind the egress gateway | `192.168.1.0/24` |

In this case, the client machine cannot properly determine where traffic for `192.168.1.x` should go. Most operating systems prioritize the local network route, causing traffic to stay on the local LAN instead of being sent through the egress gateway.

As a result:

* Remote resources become unreachable
* Routing behaves unpredictably
* Site-to-site and remote access connectivity may fail

### How Netmaker Solves This

Netmaker solves overlapping subnet conflicts using [**Virtual NAT mode**](https://learn.netmaker.io/features/egress?q=virtual#virtual-nat-mode-the-solution-for-egress-routes) for Egress Routes.

With Virtual NAT enabled:

* The real remote subnet remains unchanged
* Netmaker assigns a unique virtual subnet for clients
* The egress node automatically translates traffic between the virtual and real IP ranges

#### Example

| Actual Remote Network | Virtual NAT Range |
| --------------------- | ----------------- |
| `192.168.1.0/24`      | `198.19.10.0/24`  |

Instead of accessing the remote network directly through `192.168.1.x`, clients use the assigned virtual subnet. The egress gateway then handles the IP translation automatically.

This avoids conflicts with the user’s local routing table while maintaining seamless connectivity to remote resources.

### Benefits

* Eliminates overlapping subnet conflicts
* No need to renumber existing networks
* Simplifies remote access deployments
* Supports multiple sites using identical private IP ranges

### Conclusion

Egress Route conflicts with local network routes are common in environments where overlapping private IP ranges exist. By using [Virtual NAT mode](https://learn.netmaker.io/features/egress?q=virtual#virtual-nat-mode-the-solution-for-egress-routes), Netmaker allows clients to access remote networks reliably without changing existing infrastructure or creating complex manual NAT rules.


---

# 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 dynamically by asking a question.

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

```
GET https://learn.netmaker.io/help-articles/egress-route-conflict-with-local-network-route.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.