About IP addresses
Every device that connects to the internet has its own Internet Protocol (IP) address to enable identification and communication between devices. IP addresses mark where the data originates, and where it is destined.
IP addresses are either:
- Private – only visible and available within a private network.
- Public – visible and available on the internet.
IP addresses are also either:
- Static – the IP address remains constant. These are also known as fixed IP addresses.
- Dynamic – the IP address is temporary, changing automatically and regularly.
For information about how IP addresses are allocated per customer, see About secure subnets.
Eseye assigns a unique IP address to every device.
Since IPv6 support is not well adopted by MNOs, we currently use IPv4 addressing within the cellular networks. Our equipment is ready to support IPv6 addressing. If required, customisation for a particular secure subnet is possible. Contact Support for more information.
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.
The Eseye PoPs use Network Address Translation (NAT) to translate multiple private IP addresses to a single public IP address for sending device data across the internet. For more information, see About Network Address Translation (NAT).
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.
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.
Initiating communication with a device is not IoT best practice. For more information, see Configuring devices to initiate communication.
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 and are therefore prone to hacking. Mapping a static public IP address directly to a device diminishes the power of a firewall. This means that the device itself will need added security against hacking attempts.
- Increased cost and decreased scalability – IPv4 address exhaustion means that obtaining public IP addresses in large numbers is expensive, difficult, and restricts scalability. For more information, see IPv4 address exhaustion.
- Less redundancy – the singular geographic nature of a static public IP address means that the device cannot switch onto alternate routing paths, limiting the device to using a single cellular network.
- Increased latency – restricting a device to a single cellular network increases the risk of delayed data transfer, with no option to switch to faster routes.
- Reduced connectivity options – restricting a device to a single cellular network means that it could become inaccessible in the event of an Eseye PoP failover. For more information, see Configuring a device to access the correct network.