Update packets are used to exchange files with the router that are to be stored or executed on the router.

These files can be:

  • Firmware updates

  • Binary configuration files

  • ASCII configuration files

  • Containers

  • Container configurations

Different files can be bundled in a combined update packet. A manifest file defines the file(s) contained in the packet and is also part of the packet.

Situation

You have a router in the field and want to update the configuration of the router using an ASCII configuration file. The following solution describes how to bundle an update packet containing an ASCII configuration file. Other update packets can be bundled accordingly.

Solution

It is prerequisite that you have an ASCII configuration file like the one created in this Configuration Guide [1]

You still need to create an update packet containing this configuration file.

Creating the update packet

  1. Open the PowerShell on a Windows computer by hitting the Windows key () and entering powershell or open a terminal window on a Linux computer.

  2. Navigate to the directory containing the ASCII configuration file.

  3. Calculate the MD5 checksum of the configuration file:
    > md5sum ascii_config_file.txt [2]

  4. Copy the MD5 checksum to the clipboard.

  5. Create a text file with the name MANIFEST (without filename extension) and the following content:
    FILENAME=ascii_config_file.txt
    DESCRIPTION=ASCII config for update packet example [3]
    MD5SUM=paste_above_checksum_here
    FILETYPE=ASCII Configuration [4]

  6. Pack the MANIFEST file and the ASCII configuration file into the update packet:
    > tar -vcf config_packet.tar MANIFEST ascii_config_file.txt [5]

You have now created an update packet that can to be uploaded to the router.

There are different filetypes for different files and purposes. The following table shows these options:
FILETYPE Purpose

Full Software Update

Major firmware update (1.0, 2.0, 3.0 etc.)

Incremental Software Update

Minor firmware update (2.1, 2.2, 2.3 etc.)

Binary Configuration

Profile in form of a binary file

ASCII Configuration

ASCII configuration that will immediately be executed and not stored upon uploading

Stored ASCII Configuration

ASCII configuration that will be stored and not executed upon uploading

Container

Linux container

Container Configuration

Content of /data/etc of a container packed as tar archive

Uploading the update packet in the web interface

  1. Open web interface of the router using a browser: 192.168.1.1 [6]

  2. In the Administration → Up-/Download menu, go to the Upload section, click on Browse…​ and select the update packet that you have created above.

  3. Click on Upload.

The update packet will be uploaded to the router and processed accordingly.

Troubleshooting

  • The MANIFEST file must not have a file extension like .txt.

  • It is possible for Windows computers that the routine md5sum for computing the MD5 checksum is not available. In this case, the checksum an be computed using the command certutil -hashfile ascii_config_file.txt md5.

Back to the Configuration Guides for icom OS Smart Devices

Back to overview

1. You may use this ASCII configuration file for testing purposes.
2. This is just an example for an ASCII configuration file name.
3. This is just a description of the contained configuration file.
4. The spelling of the FILETYPE is important since it defines the usage of the update packet.
5. This command packs the specified files (here MANIFEST and ascii_config_file.txt) into the specified tar packet (here config_packet.tar).
6. Login depending on configuration; default for past firmware versions: User name: insys, Password: icom