 |
Online help |
Automatic update
The automatic update is used to provide devices in the field with updated firmware or configurations. To do this, you must provide a central server on which the update files and the download list are stored. The download list will then be checked by the devices if the action "Start Auto-Update" is triggered by an event.
Download list syntax
The download list is a text file (ASCII or UTF-8 without BOM) that refers to the update packet to be downloaded.
A line consists of two fields that are separated by;.
The first field contains either the device-individual serial number or*as a wildcard for all devices.
The second field contains the absolute path to the update packet.
Lines beginning with#will be ignored.
Only the first fitting line will be evaluated on each device.
Example:
16334455;/configs/profile.tar
*;/updates/autoupdate-2.0-to-2.3.tar
Sequence
In order to avoid the transmission of unnecessary data, the fields Content-MD5, ETag and Last-Modified can be evaluated from the HTTP or FTP header of the auto update server. In case of FTP, only Last-Modified will be evaluated. The Precondition for download option allows follwoing behaviour:
| Precondition for download | Behaviour |
|---|---|
| none | the download list will always be downloaded; the update packet specific to the router will always be downloaded |
| Header has changed | the download list will only be downloaded if the header has changed; the update packet specific to the router will always be downloaded |
| File name has changed | the download list will always be downloaded; the update packet specific to the router will only be downloaded if the file name has changed |
| Header and file name have changed | the download list will only be downloaded if the header has changed; the update packet specific to the router will only be downloaded if the file name has changed |
If the auto-update server does not support the header fields, the download list will always be downloaded and the file name of the update packet can be checked.
If the update packet will then be downloaded successfully, it will be stored (regardless of whether it has been modified) and the individual entries will be applied in the order listed in the manifest.
The FILETYPE ASCII Configuration will be executed immedialtely and not stored.
In case of firmware auto-update paclets, the contained ASCII Configuration will check the running firmware version and only activate the stored firmware if it is more recent than the running firmware.
The auto-update cache that stores the information for comparing the versions can be deleted when resetting the router to default settings.