Setups
General information
Wirnet™ iBTS information
Wirnet™ iFemtoCell information
Wirnet™ iFemtoCell-evolution information
Wirnet™ iStation information
System management
Network management
LoRa Features
KerOS customization
Support and resources
Setups
General information
Wirnet™ iBTS information
Wirnet™ iFemtoCell information
Wirnet™ iFemtoCell-evolution information
Wirnet™ iStation information
System management
Network management
LoRa Features
KerOS customization
Support and resources
This is an old revision of the document!
This page explains system upgrades on KerOS >= 4 and also:
The firmware is released in two formats: KerOS: and Liveburner. These have a very different behavior, so please use the appropriate file before updating.
To upgrade the system from KerOS version 3.x to KerOS version 4.x the use of a liveburner is mandatory. Two possibilities are available:
Upgrade system using a simple upgrade package (i.e. keros_4.X.Y_klk-lpbs-signed.ipk file) is only available from a source firmware version >= 4.0.
The upgrade will install the new KerOS firmware with some consequences on the data:
The upgrade process itself is the following sequence:
To upgrade your system, follow the software update process. Information here.
The upgrade will install the new KerOS firmware with some consequences on the data:
To upgrade your system, follow the software update process. Information here.
During an upgrade, the only way to keep system files (network configuration, password…) is to make a backup during the upgrade. This is done by the sysupgrade mechanism.
This mecanism is divided in 2 elements:
/etc/sysupgrade.conf: Contains the system (KerOS) elements to backup/restore in case of upgrade./etc/sysupgrade.d/: a directory with .conf files where additional elements to backup/restore can be added (i.e. by additional packages).By default, the system has a predefined list of configuration files to preserve:
File to download - /etc/sysupgrade.conf
## This file contains files and directories that should ## be preserved during an upgrade. # /etc/example.conf # System Configuration files ############# /etc/profile /etc/strongswan.conf /etc/timestamp /etc/network/ /etc/bnm/bnm.conf /etc/hosts /etc/kgpsd.conf /etc/default/ /etc/firewall.d/ /etc/ssh/ /etc/ipsec.secrets /etc/ipsec.conf /etc/monit.d/ /etc/strongswan.d/ /etc/cron/ /etc/shadow /etc/passwd /etc/udhcpc.d/50default /etc/ntp.conf # System persistant data ############ /var/log/
If a specific software also needs to keep configurations between upgrades, it is possible to add a .conf file in the /etc/sysupgrade.d directory:
File to download - /etc/sysupgrade.d/myapp.conf
## This file contains files and directories that should ## be preserved during an upgrade. /etc/myapp.conf
A specific reporting file is generated when an upgrade is done: /user/.sysupgrade.log.
Hotfix packages are only available for a specific version of the firmware. So in case of upgrade, they will be automatically removed. More information on hotfix package here.