> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/faq-fixedip/faq-fixedip-migration.md).

# FAQ - FixedIP Migration

<details>

<summary>What is fixedip.m2m?</summary>

fixed.m2m is an APN (Access Point Name) used to provide IoT devices with a public, fixed IP address, allowing direct inbound and outbound connectivity over the mobile network.\
<https://en.wikipedia.org/wiki/Access_Point_Name>

</details>

<details>

<summary>What is the difference between the old and new situation?</summary>

In the old situation (fixedip.m2m):

* Devices received a public IP address directly on the IoT device.
* There was no NAT translation, allowing direct inbound connectivity from the Internet.

In the new situation (dynamic IP allocation with INAT):

* Devices now receive a private IP address from a KPN-managed internal range.
* IMSI-aware NAT (INAT) ensures each device still has consistent connectivity to the same public IP externally.
* Functionally, communication to and from the Internet remains possible, but inbound access is now handled through NAT.

> In short: the main change is that the public IP is no longer directly assigned to the device, but connectivity remains unchanged thanks to IMSI-aware NAT.

</details>

<details>

<summary>What is an APN?</summary>

Access Point Name <https://en.wikipedia.org/wiki/Access_Point_Name>

</details>

<details>

<summary>What is NAT?</summary>

NAT translates IP addresses between private and public networks.

* SNAT (Source NAT): Translates the private source IP address to a public one when sending traffic out.
* DNAT (Destination NAT): Translates a public destination IP back to a private IP when receiving traffic.

This process enables multiple devices to share a single public IP address and helps improve network security and scalability. However KPN IoT still uses 1 IP per IoT simcard.

</details>

<details>

<summary>What makes fixedip.m2m special?</summary>

Unlike regular APNs that use NAT, fixedip.m2m provided a directly routed public IP address to your IoT device.

This meant:

* No NAT translation occurred.
* Your device could be reached directly from the Internet using its public IP.

</details>

<details>

<summary>What is IMSI-aware NAT (INAT)?</summary>

IMSI-aware NAT (INAT) dynamically links your device’s IMSI (International Mobile Subscriber Identity) to an internal, dynamic IP address.

Although the internal IP is dynamic, your device maintains consistent connectivity to the outside world through the same public (WAN) IP address.

This allows both inbound and outbound communication while still benefiting from dynamic addressing.

</details>

<details>

<summary>What does a dynamic IP address mean?</summary>

A dynamic IP address is assigned automatically from a pool of available addresses using DHCP (Dynamic Host Configuration Protocol) <https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol>.

It may change over time or after a device reconnects to the network.

***

</details>

<details>

<summary>Where does my dynamic IP address live?</summary>

Your dynamic IP is assigned within a private IP range, managed internally by KPN.

It is not directly accessible from the public Internet but is translated through NAT for external communication.

</details>

<details>

<summary>What is a private IP range?</summary>

A private IP range refers to IP addresses reserved for internal network use only.

They are not routable on the Internet. Common private ranges include:

* 10.0.0.0 – 10.255.255.255
* 172.16.0.0 – 172.31.255.255
* 192.168.0.0 – 192.168.255.255

<https://en.wikipedia.org/wiki/Private_network>

</details>

<details>

<summary>Where can I find my public IP address?</summary>

Your public IP address can be found in Cisco Jasper (Control Center) — just like before.

This applies to both the previous fixedip.m2m setup and the new dynamic IP configuration.

There is no change in how you access or view this information.

</details>

<details>

<summary>Do I need to migrate my devices after testing?</summary>

**No.**

KPN will automatically convert fixedip.m2m to use dynamic IP assignment.

This ensures your IoT devices remain connected without requiring reconfiguration.

</details>

<details>

<summary>Where can I configure the test APN and communication plan?</summary>

* You can configure the test APN in your IoT device.
* The communication plan directly in Cisco Jasper (Control Center).

</details>


---

# 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.kpnthings.com/kpn-things/faq-fixedip/faq-fixedip-migration.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.