> 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.md).

# IP addressing and routing

Every internet-connected device has an Internet Protocol (IP) address. IP addresses identify devices and indicate data origins and destinations.

IP addresses have these visibility options:

* **Private:** Visible only within a private network.
* **Public:** Visible on the internet.

IP addresses also have these assignment options:

* **Static:** The IP address remains constant. These are also called fixed IP addresses.
* **Dynamic:** The IP address changes automatically and regularly.

See [About secure subnets](/anynet-sim/connectivity/ip-addressing-and-routing/about-secure-subnets.md) for customer IP address allocation.

Eseye assigns a unique IP address to every device.

![Private device addresses translated to a public egress address](https://2995386447-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzlTL8FVu6GaQkB5i1TRY%2Fuploads%2FMpu9DpqlI4sGNGPXmBdb%2FConnectivity_DeviceIPAddresses.svg?alt=media)

{% hint style="info" %}
MNO IPv6 support remains limited. Eseye uses IPv4 addressing within cellular networks. Eseye equipment supports IPv6 addressing. Contact Support about secure-subnet customization.
{% endhint %}

## Assigning private IP addresses to devices

Eseye usually assigns private static IP addresses to customer devices, one per IMSI, for the lifetime of the device.

Eseye PoPs use [Network Address Translation (NAT)](/anynet-sim/connectivity/ip-addressing-and-routing/about-network-address-translation-nat.md) to translate multiple private IP addresses to one public IP address for sending device data across the internet.

Each PoP has one or more public IP addresses to egress data across the internet to the customer network. For more information, see [Egress IP addresses](/anynet-sim/connectivity/ip-addressing-and-routing/egress-ip-addresses.md).

## Assigning static public IP addresses to devices

Usually, a customer requests static public IP addresses because they want to initiate communication with devices at any time. For example, an engineer might want to use a laptop with the Wi-Fi in an internet café to bring up a terminal session on remote equipment.

{% hint style="warning" %}
Initiating communication with a device is not IoT best practice. For more information, see [Configuring devices to initiate communication](/anynet-sim/connectivity/device-configuration-best-practices.md#configuring-devices-to-initiate-communication).
{% endhint %}

Using static public IP addresses for IoT devices is not recommended for a number of reasons:

* **Increased security risks:** Device IP addresses are accessible to anyone with an internet connection. Mapping a static public IP address directly to a device limits firewall protections. The device needs added security against hacking attempts.
* **Increased cost and decreased scalability:** IPv4 address exhaustion makes large public IP address allocations expensive and difficult. It also restricts scalability.
* **Less redundancy:** A static public IP address restricts a device to one cellular network and routing path.
* **Increased latency:** Restricting a device to one cellular network can delay data transfer. The device cannot switch to faster routes.
* **Reduced connectivity options:** A device can become inaccessible during an Eseye PoP failover. For more information, see [Configuring a device to access the correct network](/anynet-sim/connectivity/section-a-connecting-over-the-mobile-network.md#configuring-a-device-to-access-the-correct-network).


---

# 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.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.