---
title: "How does the renaming of the cellular interface from lteX to cellularX affect my application?"
slug: "how-does-the-renaming-of-the-cellular-interface-from-ltex-to-cellularx-affect-my"
updated: 2026-08-06T13:17:40Z
published: 2026-08-06T13:17:40Z
canonical: "docs.insys-icom.com/how-does-the-renaming-of-the-cellular-interface-from-ltex-to-cellularx-affect-my"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insys-icom.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How does the renaming of the cellular interface from lteX to cellularX affect my application?

The cellular interfaces have been renamed from `lteX` to `cellularX` with **icom OS 10.0**, for example the interface `lte2` has changed to `cellular2`. The sequence number `X` refers to the slot where the cellular card is inserted in an MRX router or the virtual slot of a compact router.

To ensure a smooth transition, icom OS 10.0 provides extensive backward compatibility:

- **Update:** During the update to icom OS 10.0, all interface references in the device configuration are automatically renamed from `lteX` to `cellularX`. This includes references used throughout the system, such as [routing](/kb/docs/routing-en), [firewall rules](/kb/docs/netfilters-en), [WAN chains](/kb/docs/wan-chains-and-wan-groups-en), and other configuration areas. No manual changes are required.
- **Downgrade:** When downgrading from icom OS 10.0 to an earlier release, interface names are automatically converted back from `cellularX` to `lteX`.
- **Binary Profile import:** When importing binary configuration [profiles](/kb/docs/profiles-and-profile-handling-en) created with earlier icom OS versions, interface names are converted automatically during import.
- **CLI and LUA:** The legacy `lteX` interface names remain fully supported in the [CLI](/kb/docs/command-line-interface-cli-en). Commands using either `lteX` or `cellularX` are accepted and treated identically.
- **ASCII config:** Existing [ASCII configuration files](/kb/docs/ascii-configuration-files-en) remain fully compatible and do not require any modifications.
- **Scripts and Containers:** Existing automated integrations, such as scripts running in LXC [containers](/kb/docs/containers-en), can continue using the legacy interface names.
- **REST API:** The [REST API](/kb/docs/working-with-the-rest-interface-en) likewise continues to accept the legacy `lteX` interface names for compatibility.

> [!WARNING]
> Please note for binary configuration profiles!
> 
> Binary configuration files created with icom OS 10.0 use the new `cellularX` interface names. While these profiles can be imported into older icom OS versions, the interface references are not converted automatically. As a result, the imported configuration will not operate correctly.

> [!NOTE]
> Please note for **CLI output, REST API responses, and variable substitutions!**
> 
> Using `$CLI` or `$REST` now return the new `cellularX` interface names. While existing commands and API requests using `lteX` remain fully compatible, scripts, notifications (e.g. e-mails or SMS messages), and HTTP requests that process returned interface names may need to be updated.