icom OS

icom OS Release Notes

Firmware Download

icom OS 5.0 is the minimum required version for icom OS 8.5.1 update

Update Packet for Manual Update Update Packet for Auto-Update Server
8.0-to-8.5.1 incremental

sha256: bbc4aa9933f4a2403c572e2529447de30fc08bd3d7307555f9407fb28a27a4b6

8.0-to-8.5.1 incremental

sha256: aec6c2f7625da024fb7c96bb212f0930b4773f04d87c5613510c5412d5fd75c2

8.5.1 full package

sha256: 9faebc952e4e79616e633518309159b080cd81c7c0da8303071ed57b5adce956

8.5.1 full package

sha256: 2b558dc4e0daf56a27771406cf4f1ca25908edfc7dba8b810ba387dfb4a55946

Signed Update Packet for Manual Update Signed Update Packet for Auto-Update Server
8.0-to-8.5.1 incremental

sha256: 1bc41565e8819235091f821186f8f9f5611a18771c0467051fd24280cd0e6bf2

8.0-to-8.5.1 incremental

sha256: 2701d511506efba53b9dde57a69d50c51df30b1948f68f4de360ea4fb35b9dd3

8.5.1 full package

sha256: 501ccafba7347c73c000a2b2b1f6502c63443b11840b5863c36cf9a112558e90

8.5.1 full package

sha256: 58f259d8feb6fb76dadc4656339836d2c55bfde7bc9fba7562cd52b072c00304

Certificates
insys_sub_ca_icomos_v1_exp_20340814.pem Intermediate CA that issues device individual HTTPS server certificates.
insys_root_ca_v1_exp_20330525.pem Root CA that issued the certificate "insys_sub_ca_icomos_v1_exp_20340814.pem".
icom_firmware.crt Used to verify signed firmware packets.
icom_ca.crt Certification Authority that issued the certificate "icom-firmware.crt".

Explanation of Update Packets


Type of Update Packet

Update Packet for Manual Update: Use it to update a device by uploading the update packet to the router and then activate the firmware.

Update Packet for Auto-Update Server: Use it if you have set up your own Auto-Update server. The packets contain an ASCII configuration file that ensures an automated activation of the firmware after being downloaded from the server.

Size of Update Packet

Incremental packets "6.0-to-6.x": Are smaller in size to save bandwith and are used for updates between minor releases e.g. from 6.3 to 6.4

Full packets "6.x full": Contain the entire firmware and are used to update across major releases, e.g. from 5.3 to 6.8.
Attention: major releases can affect up- or downward compatibility (depending on configuration).

Verification of Update Packet

Regular Update Packets: For most users this is the right update packet. Security: the firmware in the update packet is signed and encrypted and the router will only accept firmware signed by INSYS.

Signed Update Packets: Use these update packets when the advanced function *Allow only signed update packets* under *Administration>Automatic Update* was activated. Security: the entire update packet (not only the firmware image) needs to be signed either by the INSYS CA or by your own CA.
Please only activate this option when you exactly know what you are doing! It has impact on the functioning of icom Connectivity Suite and icom Router Management.


Frequent Questions

Which update packet shall I use?

If you are unsure, use the Manual Update Packet full

When shall I use incremental over full?

When you have 1.000 LTE devices in the field and do 6 updates per year, it makes a big difference on your SIM-bill wether you pick the packet type full or incremental. Use incremental in this case.

My device has an old FW version of 3.x and updates to latest firmware is failing

Update to version 4.0 first and then continue with newer versions. All firmware following 4.0 have been signed with a new certificate that is not known in 3.x versions.


Here you can download

icom OS 4.0 full

icom OS 4.0 - 4.6

icom OS 5.0 full

icom OS 5.0 full autoupdate

icom OS 6.0 full autoupdate

icom OS 7.0 full


Download Releasenotes as .txt-file:


bugfix: icom OS 8.5.1

⚠️ Known Issue:

APN settings (since icom OS 8.5): On MRX with worldwide engine a change of the APN has no effect. This also applies for first setup, when the APN is set for the first time.

  • Effect:
    • If 8.5 is used for initial setup of the device, no internet connection can be established
    • If the APN is changed later on, the device will still uses the previous APN
    • This will not change after furter reboots
  • Affected devices:
    • MRX2 LTES 1.1
    • MRX3 LTE 1.2
    • MRX5 LTE 1.2
    • Other devices (other MRX, MIRO, SCR, ECR) are not affected
  • Recommendation: We recommend to stay on icom OS 8.4 for the affected devices.
  • Fix: Issue will be resolved in upcoming icom OS 8.6 (in about two weeks)
bugfix
  • NAT rules with port ranges: NAT rules (SNAT, DNAT, or port forwarding) with different port ranges for destination and NAT ports are accepted and correctly created (Known Issue since 8.4)

  • Forwarding filter rules: If multiple input and output interfaces are specified, all combinations are created as individual rules (Known issue since 8.5)

  • EST: Retrieved CA certificates can be used for other TLS services (i.e. autoupdate, e-mail) directly after enrolment

  • Autoupdate: Special characters in $cli() - placeholder answers are correctly escaped in HTTP endpoint

  • MIRO-L110 and MIRO-L210: Clock is correctly initialized via cellular network


feature: icom OS 8.5

⚠️ Known Issues:

  • NAT rules (since icom OS 8.4): If a port range is mapped to a single port (SNAT, DNAT, or port forwarding), the rule is not applied.
  • Forwarding filter rules (since icom OS 8.5): If multiple input and output interfaces are specified, not all possible combinations are created as individual rules.

Note: If you rely on these functions, we recommend not updating to this version for now. A fixed version will be available soon.

feature
  • LTE: IPv6 Support for Mobile Connections

    On MIRO, SCR, and ECR devices, mobile connections now support IPv6 and Dual-Stack (IPv4/IPv6) connections, depending on the SIM card.

    Note: Devices configured as IPv6-Only with the new firmware will not be able to connect via IPv4 after a downgrade unless a factory reset is performed.

  • LTE: Scan for available cellular providers

    The device can now scan for all available mobile providers and technologies. The scan can be triggered manually via the UI or automatically based on events. A follow-up action can be executed after completion.

    Results are displayed in the UI. On MRX LTE450 and MIRO L-230, frequency bands and signal values are also shown.

    Note: The scan may take several minutes. If the device is connected via mobile network, it will be offline during the scan. 

    Known Issue: In the UI, the correct RSRP/RSRQ values are displayed for 4G cells, but they are incorrectly labeled as RSCP/RSRQ.

  • Messages: In addition to existing placeholders, the device now supports $rest(/status/XYZ), which is replaced with the corresponding JSON output from the device's REST API when the message is sent

    Example:
    $rest(/status/sysdetail/system)
    returns

    {
     "status": {
     "unique": {
     "location": "My location",
     "date": "2025-03-12 10:28:57",
     "uptime": "2 h 23 min ",
     "load": "0.04 0.06 0.07",
     "ram": "373796 kByte free",
     "hash": "BC590282",
     "mac": "00:05:B6:03:1B:EC",
     "remote_management": "active, offline",
     ...
     }
     }
    }
update
  • Dashboard: new widgets and content of dialogs added

    • DSL dialog
    • Container dialog
    • Input/output dialog
    • WLAN widget and dialog
    • Network widget is expanable
    • Design, layout and other minor improvements

  • icom Router Management: Router tries to connect to iRM every time the wan chain is online to speed up iRM connect time

  • IPv6: IPv6-Addresses for LTE connections are displayed in status

  • SNMP: Company name of enterprise MIB changed to "INSYS icom GmbH" (enterprise OID 34081 remains unchanged)

  • Linux kernel: Linux kernel patched (fixes CVE-2024-50302)

  • axios OSS package update: updated to version 1.8.2

bugfix
  • Firewall: Rules with identical start and end port are not ignored (bug introduced in 8.4)

  • SCR/ECR: Fixed LTE connection if PPP uses same local and remote IP address

  • SCR/ECR: Fixed LTE connection in case the provider does not set the PDP context

  • LTE: Handling of some error messages from modem improved (results in quicker connection reestablishment, depending on error)

  • WAN-Status: Status values are correctly reset when WAN chain goes offline

  • UI: Usability issues with navigation in collapsed mode are resolved

  • UI: IPv6-Adresses can be configured for routing and firewall rules

  • MIRO-L230: Flash status is available as status value

  • LTE Status: LTE status values are longer preserved in case new values can currently not be retrieved

  • CLI: Result of SMS sending is returned properly

  • Debugging: Manual AT commands are correctly answered regardless of upper or lower case


feature: icom OS 8.4

New Dashboard – Better Overview, More Control

With this release, the Web-GUI gets a completely redesigned dashboard, replacing the previous one.

The new dashboard offers:

  • Clear network overview – Instantly see local interfaces, WAN connections, and VPN tunnels.
  • Seamless integration of INSYS icom services – Direct access to the icom Connectivity Suite – VPN and icom Router Management.
  • Essential system information – Serial number, firmware version, and more at a glance.
  • Status of all active and inactive services – Firewall, configuration access, automatic updates, and more in one view.
  • Expandable widgets – Detailed status information for all interfaces and services.
  • Expert information for in-depth analysis – Insights into firewall rules, routing tables, and interface statistics.
  • Quick links to configuration pages – Instantly navigate to the relevant settings.
  • Connection check via Ping – Diagnose network issues with a single click.

Coming soon:
Some extended dialogs and detailed views will be added in the next two icom OS releases, including:

  • Extended DSL information
  • Container status
  • I/O status
  • Wi-Fi widget with additional details
feature
  • UI: new Dashboard with all status information and direct links to the configuration

  • Logging: all log messages now contain a severity

  • Syslog: message format can be selected and now support RFC 5424 and RFC 3164

  • Syslog: severity level can be selected to adjust the amount of sent syslog messages

update
  • Status: routing table in CLI and REST shows IPv6 routes (not only IPv4)

  • Debugging: timeout for AT commands increased to support longer running AT commands

bugfix
  • IPsec: modified tunnel establishment to support broken setups with some specific cisco setups

  • Firewall: whitespaces in configuration options no longer causes rules to not load

  • Firewall: missing 'protocol' field falls back to 'all'

  • Firewall: skip rules with invalid port range

  • SFP/Fiber: fixed issue for certain scenarios which include VLAN Trunks on SFP/Fiber

  • LTE: fixed issue to register to network with some specific SIM cards


feature: icom OS 8.3

feature
  • IPsec: up to 20 additional IPsec SAs can be used for each IPsec tunnel to tunnel different subnets

update
  • DynDNS: providers Duck DNS and dynv6 available

  • New UI: configuration page for MCIP (events) available

bugfix
  • HTTPS: certificate based client authentication is not disabled, if expired device individual certificate is used as HTTPS certificate

  • LTE450: if two data channels are active, routes are set correctly

  • LTE: if network registration is not successful within 12 hours, the modem is restartet

  • LTE: reduced extensive log messages if PIN is needed but not provided

  • Profile Activation: suppressed false error log message about unavailable Parameters on profile activation


update: icom OS 8.2

feature
  • OpenVPN: terminate UDP tunnels with explicit-exit-notify

  • Firewall: Added protocol OSPF to be selected for Firewall, SNAT and DNAT rules

update
  • curl OSS package update: updated to version 8.11.0 (fixes CVE-2024-2398)

  • dnsmasq OSS package update: updated to version 2.90 (fixes CVE-2023-28450)

  • mosquitto OSS package update: updated to version 2.0.20 (fixes CVE-2023-28366 and CVE-2024-8376)

  • curl CA bundle OSS package update: updated to version 2024-09-24

  • metalog OSS package update: updated to version 20230719

  • axios OSS package update: updated to version 1.7.7

bugfix
  • File Upload: Fixed detection of file type for uploads via REST API or new UI

  • SMS sending and reception: improved reliability of SMS sending and reception

  • Classic UI: prevent webserver crash if special characters are used for IP net descriptions

  • Status values: show correct uptime of IP net with multiple static IP addresses


update: icom OS 8.1

New INSYS icom PKI

Within the next months, INSYS icom will use a new CA certificate to issue the device individual certificates which are provisioned during production.

All devices, which have a serial number 24136331 or higher and MAC address 00:05:B6:12:E1:23 and higher will already have and use a "new" certificate.

Impact on device behavior

For all devices which have a new certificate and are running with a firmware 8.0 or lower it will have two effects

  1. as the old firmware doesn't know the new CA, it will display a warning message in the classic UI that "the configured HTTPS certificate is not issued by the configured CA certificate". This is just a warning and can be ignored, as the HTTPS connection still works.
  2. if client authentication via certificates is configured and the device individual certificate is used as server certificate, the client authentication via certificates is deactivated. If no fallback username/password is configured these devices won't be accessible via HTTPS any longer


For all devices already shipped, this will not affect the applications, the behavior or the connection. Also an update to 8.1 will not affect already shipped devices.

Mitigation

Both effects can be mitigated on icom OS 7.6 or higher by uploading the new certificate chain (root CA and intermediate CA) onto the device and select the intermediate CA as "CA certificate for HTTPS".

In general INSYS icom always recommends using an own PKI for the HTTPS server certificates and client authentication via certificates. In this case, none of the above effects will arise.

update
  • IP networks: colours of the ip networks (for device graphics) are now configurable

  • Container: Static information about the device (i.e. serial number, firmware version) is available in the container at /devices/device_info.json

bugfix
  • RSTP: works on trunk ports

  • MRX LTE: Connection is stable if MTU of LTE interface is lower than 1500 and packets through a VPN tunnel exceed the MTU

  • Container: network interfaces bridged to a container can be IPv6 only

  • Container: container still starts if bridged network is deleted from the config

  • Fiber/Ethernet: SFP slots and ethernet ports on MRcards ES are reliably initialised on start

  • PPPoE: ip networks in PPPoE mode work again, if ip network list is altered


feature: icom OS 8.0

feature
  • Now up to 100 IP networks configurable:

    With icom OS 8.0 the previous limitation to 5 ip networks was resolved. Up to 100 IP networks can now be created. Also additional DHCP servers (IPv4 and IPv6) can be added.

    To ensure downward and upward compatibility, the firmware behaves as follows

    • on update to 8.0 (or higher) all active networks of the previous 5 ip networks will be transferred into the new list of ip network
    • on downdate to a firmware lower than 8.0, the ip networks with name "net1" to "net5" are transformed into the old networks
    • even though the syntax of the cli changes for the new ip networks, old ascii configurations will still be interpreted correctly
    • binary profiles will be converted into the new ip network list on import

    Caution:

    • Binary profiles created with firmware 8.0 or higher will lead to unspecified behavior, when imported into firmware lower than 8.0
    • ascii configurations created with firmware 8.0 or higher will not result in the expected configuration, when imported into firmware lower than 8.0

update
  • OpenSSL OSS package update: updated to version 3.1.7

  • OpenVPN OSS package update: updated to version 2.6.12 (fixes CVE-2023-46849 and CVE-2023-46850)

  • pam_radius OSS package update: updated to version 3.0.0 (fixes CVE-2024-3596)

bugfix
  • REST-API-Documentation: OpenAPI documentation was not valid according to the OpenAPI specification

  • classic UI: increased some timeouts (for firmware activation and reset) to prevent false error messages


update: icom OS 7.9

update
  • dropbear OSS package update: updated to version 2024.85 (fixes CVE-2023-48795)

bugfix
  • ECR-LW300 1.1: sending SMS through GSM supports special characters

  • MRcards: fixed sporadic communication issues between MRcards

  • Signed and encrypted update packages: empty private keys (like the placeholder key) do not cause decrypting of additionally encrypted update packages to fail

  • UI: after import of icom Router Management start configuration the profile activate can be clicked again

  • UI: Upload of more complex configurations (i.e. including Containers, Container-Data, multiple stored ASCIIs) on the welcome page are correctly applied

  • Classic UI: fixed some Javascript errors which resulted in not correctly hidden config options


feature: icom OS 7.8

feature
  • User Interface Language: language support added for French, Italian, Spanish and Chinese.

  • Device metrics: multiple device metrics are now continuously calculated and available for analytics:

    - Counter of boot processes since production
    - Counter of boot processes since reset
    - Operating hours counter
    - Online counter since production
    - Online counter since reset
    - Online counter since last boot process
    - Timestamp of last successfull online connection

    The new metrics are displayed in the webinterface or can be read through CLI or REST API.

  • New Ping Event: a Ping check (icmp) is now available as event and action in the Event/Action toolbox. Multiple configuration parameters available: number of retries, timeouts and state change.

  • New DNS Event: a DNS check is now available as event and action in the Event/Action toolbox.

update
  • New UI: configuration page for I/Os (input/output) available.

  • New UI: non functional optical changes: max width set to 1920px, navigation changed to 'single column navigation'.

  • LTE450: update of cellular engine firmware is possible for MRcard LTE450.

  • icom Router Management: server certficate can be verfied using OCSP-stapling.

  • Auto-Update: server certficate can be verfied using OCSP-stapling.

  • IPsec: certificate revocation policy is now configurable for OCSP or CRL (cert. revocation list).

  • EST protocol: If the server certificate check fails, the CA certificates are retrieved without a server check and a new trustchain is created.

bugfix
  • Modem State Machine: internal changes to the modem state machine fixes multiple support cases in relation with cellular connectivity.

  • Package loss: Packages with special sizes are sent reliably with certain SIM cards (e.g. mdex). Products affected: MRX3 LTE 1.1, MRX5 LTE 1.1, MRX2 LTES 1.0, MRcard PL 1.0

  • Connection stability: cellular connection remains stable also for packets with certain fragmentation. Products affected: MRX3 LTE 1.2, MRX5 LTE 1.2, MRX2 LTES 1.1, MRcard PL 1.1.

  • Known Issue: on ECR-LW300 1.1 with icom OS 7.8 when sending SMS through GSM, special characters are not working.


feature: icom OS 7.7

feature
  • EST: The EST Protocol (Enrollment over Secure Transport) is now available use for secure Certificate Enrollment.

update
  • SCEP removed: the Simple Certificate Enrollment Protocol was removed in this version and is no longer available in icom OS. We suggest all users to use the now available EST protocol instead, which only has advantages.

  • New UI: the configuration page for Serial-Ethernet-Gateway was added.

  • System status: a new system status value was introduced, containing the minimum required icom OS firmware version for each individual device. The version depends on the respective hardware variant and is available through CLI and REST and will follow soon in the User Interface. A firmware downdate below this version is not possible.

bugfix
  • Port mirroring: the debugging functionality port mirroring is now supported for all interfaces, not only for LAN interfaces on the same switch. (*this debugging option is not yet available in the new user interface, but will follow soon).

  • IPsec: usage of keys using elliptic curves EC(DSA) was fixed.

  • Real Time Clock: restoring the system time from the RTC (real time clock) is working again for all MRX and SCR/ECR routers.

  • UI: cogwheel indicating firmware activiation was fixed - is now turning again.