> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/anynet-sim/connectivity/ip-addressing-and-routing/routing-non-vpn-network-traffic.md).

# Routing non-VPN network traffic

Some customers may choose to route only some, or no network traffic through [VPN](https://docs.eseye.com/glossary/) tunnels. For example, they may not require a VPN, or may have some data for transferring to destinations other than their central system, such as partner systems.

The AnyNet solution provides two options for routing non-VPN traffic:

* If full internet access is allowed, the traffic is permitted to egress onto the internet for onward routing to its destination, with no restrictions.
* With restricted internet access, the traffic is checked against a customer-supplied Access Control List (ACL) and discarded unless the destination matches one of the destinations in the list.

### About the AnyNet ACL service <a href="#about" id="about"></a>

Access Control List (ACL) rules are configured on the Eseye PoP and customer firewalls to control non-VPN traffic from devices:

* Rules on Eseye PoP firewalls determine whether incoming non-VPN traffic from devices is allowed to egress onto the internet

{% hint style="info" %}
If you want to use ACL rules for this, Eseye must configure secure subnets for your devices. You must supply the configuration information for the rules, using the [AnyNet Subnet and Security Options Order Form (XLS, download)](https://docs.eseye.com/resources/).

*Contact your Account Manager if you want to configure ACL rules at the Eseye PoPs.*
{% endhint %}

* Rules on customer firewalls permit non-VPN traffic received from an Eseye PoP to route to its destination

{% hint style="info" %}
If you want to use ACL rules for this, you must add the Eseye PoP public IP addresses or address ranges to your rules to ensure that device traffic can route to its destination. For more information, see [Egress IP addresses](/anynet-sim/connectivity/ip-addressing-and-routing/egress-ip-addresses.md).

If your devices have static (fixed) [IP addresses](/anynet-sim/connectivity/ip-addressing-and-routing.md#assigning-static-public-ip-addresses-to-devices), you must also add these addresses to your ACL rules.
{% 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 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://docs.eseye.com/anynet-sim/connectivity/ip-addressing-and-routing/routing-non-vpn-network-traffic.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.