One section per task, in the order a device meets them.
Where a guide asks you to do something, it links to the section here. Use the list of tasks, or follow the link.
The device never makes one by itself. Make one before every change: it is also where automatic recovery returns to.
The device keeps one backup: if one already exists, it asks before overwriting it. On the same tab, Automatic Failback Enable is what uses this backup when the device cannot boot; the device's own help says not to disable it unless there are special circumstances.
The backup is stored on the device itself. For a copy that survives the device, take a clone package (see Updating Your Device) and export the configuration file.
From the same tab. The device asks before it restores.
The recording stops at the confirmation question: nothing was reset on the recording device.
There is no button to download a backup to your computer. The copy you keep off the device is the clone package plus the exported configuration file.
Your settings, as one XML file on your computer.
config.xml.Settings only: not your packages, apps, containers or data. Keep it with the clone package of the same device.
The same page, the other way round. Check the two switches before you click Import.
The device does not ask for confirmation after Import. The recording stops before that click. What happens next, and what to check afterwards, is in Setting Up Your Devices.
Also the step to repeat after a default-configuration restore, which switches it off.
Devices that Robustel pre-registered to your RCMS account and switched on at the factory already have it on.
The Web UI account. Old password once, the new one twice.
The recording shows the form filled with placeholders and stops before Submit.
Only if you use the USB update path. The factory key is the same on every unit.
1. Set a new key, from the command line (logged in over SSH as your sudo user):
sudo uci set user_management.usb_key "$(openssl rand -hex 24)"sudo uci commit2. Export the matching key file, in the Web UI:
key: it goes on the USB stick with the package.From then on only the new key file is accepted: on the recording device, a key file made with the factory key was refused after the change, and the new one accepted. Keep the file with your deployment secrets.
Check your SSH access afterwards. Applying the change also re-applies the device's user settings. On the recording device this removed the SSH keys in the sudo user's ~/.ssh/authorized_keys: log in with the password and add your key again.
A clone carries the reference unit's SSH host keys and certificates. Give each device its own.
SSH host keys, from the command line on each device:
sudo rm /etc/ssh/ssh_host_*sudo dpkg-reconfigure openssh-serverThis creates new host keys and restarts the SSH server. Check the new fingerprint with:
ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pubYour SSH client will then warn that the device's host key has changed. That is expected: remove the old entry for the device from your client's known hosts and connect again. On the recording device the new key stayed after a restart.
The Web UI certificate, with a certificate and private key your own certificate authority issued for this device:
On the recording device the Web UI then served the new certificate. To go back, delete both files on the Web tab, set both fields on the Web Server page to None, then Submit and Save & Apply.
The Certificate Manager has matching OpenVPN and IPsec tabs for VPN certificates.
A port you publish with Docker can be reached from outside. Two rules keep it to the LAN.
-N DOCKER-USER1880 with your container's port:-I DOCKER-USER ! -i br_lan -o docker0 -p tcp --dport 1880 -j DROPThe rule blocks the port for traffic that does not come in on the LAN side (br_lan). On the recording device the container still answered on the device itself; from the other network it was blocked.
Keep the first rule, and keep it first. The device firewall starts before Docker. Without rule 1, on the recording device the blocking rule was not in force after a restart and the port was open again. With both rules it was blocked at the first check after a restart and stayed blocked. While Docker is running, the device logs "Chain already exists" for rule 1: that is expected.
To check that the block is in force, on the device:
sudo iptables -S DOCKER-USERThe answer lists your rule with -j DROP at the end.
Before anything that erases containers. Shown with a Node-RED container.
On the device (replace node-red and /data with your container and its data folder):
sudo docker cp node-red:/data ./node-red-datasudo tar czf node-red-data.tar.gz node-red-dataThen on your computer (replace the user and the device address with yours):
scp <user>@<device-address>:node-red-data.tar.gz .By default the logs are kept in memory and lost at reboot.
The device's own help advises against keeping the logs on NVM for a long time: set it back to RAM when you no longer need it.
Read them in the Web UI, or download the whole journal.
Logs from before the last restart are there only if you kept logs after a restart.
Settings back to default; your software stays. It switches RCMS off.
The device does not ask for confirmation. The recording stops before that click.
Afterwards, switch RCMS on again if you use it.
Returns the device to its factory baseline and deletes its backup. Export first.
Before you start: export the configuration file and take a clone package off the device (Updating Your Device).
The recording stops at the confirmation question: nothing was reset on the recording device.
What the factory baseline contains on your units: What's on Your Device.
In the Robustel knowledge base. Open the page and use its Follow button.
Fleets in RCMS also see available updates there.
Firmware is published per model in the Robustel knowledge base.
How to install each kind of package: Updating Your Device.
Customer Image Signing, RobustOS Pro 2.5.0 and later. Ubuntu 22.04, natively or under WSL. Once per PC.
Run on a Windows PC under WSL with Ubuntu 22.04, the environment the signing tool is made for. In PowerShell, as administrator:
wsl --install -d Ubuntu-22.04Signing rebuilds a system image of several hundred megabytes. Give WSL 4 GB of memory: create C:\Users\<you>\.wslconfig with these two lines, then run wsl --shutdown and open Ubuntu again.
[wsl2]memory=4GBIn Ubuntu, install the tools, then dpkg-sig from the Debian 11 archive (Ubuntu no longer ships it):
sudo apt-get updatesudo apt-get install -y squashfs-tools xz-utils binutils gnupg openssl fakeroot pv coreutils dpkg-dev file libconfig-file-perl libdpkg-perl liblocale-gettext-perlsudo dpkg -i dpkg-sig_0.13.1+nmu4_all.debMake the workspace in your Linux home folder, not under /mnt/c/, and put the signing tool (from Robustel support) and the factory firmware file in it. explorer.exe . opens it in Windows Explorer.
mkdir -p ~/repack-work/keys && cd ~/repack-workexplorer.exe .chmod +x rbt-repack-firmware.shFour files in keys/. Copy them to offline storage before you go further.
The package key. Answer 1 (RSA and RSA), 3072, 0 (does not expire), y, your name and e-mail, then O. GnuPG asks for a passphrase in its own box. Then export both halves into keys/:
gpg --full-generate-keygpg --armor --export <your-email> > keys/gpg.pubgpg --armor --export-secret-keys <your-email> > keys/gpg.keyThe system-image key. ECDSA P-256 only; the device refuses RSA:
openssl ecparam -genkey -name prime256v1 -out keys/sqfs-priv.keyopenssl ec -in keys/sqfs-priv.key -pubout -out keys/sqfs-pub.keyCopy the whole keys/ folder now to two offline places. sqfs-pub.key is the key the device locks to; without the private keys an enrolled device can never be upgraded again.
One command. About three minutes on the recording PC.
sudo ./rbt-repack-firmware.sh --package <model>-firmware-<version>.bin --gpg-pub keys/gpg.pub --gpg-priv keys/gpg.key --sqfs-pub keys/sqfs-pub.key --sqfs-priv keys/sqfs-priv.key --version <your-version> --name <your-name>If your package key has a passphrase, GnuPG asks for it in its box near the end. The tool documents a .env file for the passphrase: on the version tested here, a run with that file present stops at once with an error, so type the passphrase instead.
The new file is written next to the original: <model>-image-<your-name>_<base-version>_<your-version>_<date>.bin.
Import your package key, install, restart, then log in at once with the factory login.
1. Let the device trust your package key (over SSH, as the sudo user). Copy keys/gpg.pub to the device, then:
sudo /usr/scripts/rbt_gpg_usr.sh action=import key_file=$HOME/gpg.publs /etc/upgrade-keys/customer.dThe second command shows your key as a file. Without it the device refuses your image and deletes the uploaded file.
2. Install, in the Web UI: System → Update, Choose File, Install. After the upload the device asks "All user data will be destroyed after the upgrade. Continue?". OK installs; the device then offers to restart.
Or over SSH: the same check and installation, in under a minute. It does not restart by itself.
sudo sysupgrade $HOME/<model>-image-<...>.binsudo reboot3. Log in at once. The device is back after about two minutes, with its factory configuration and factory login. Log in to the Web UI as soon as the login page appears: until someone logs in, it restarts again about every two minutes. Then create the sudo user again and import your configuration file.
The Linux login for SSH. One per device. A signed-image installation removes it.
Recorded on an EG5200 running RobustOS Pro 2.5.0, right after a signed-image installation had removed the previous sudo user.
Key Enrolled on the Dashboard, your label on the command line.
Dashboard → System Information → Customer Image Signing reads Key Enrolled. Over SSH:
cat /etc/version-imagesudo rbt-system-mgmt developer-mode statels /etc/upgrade-keys/customer.dAfter the restart the imported package key is gone. Import it again before the next upgrade.
Two procedures with no published step-by-step yet.
| Next · step 11 of 13Keeping secure over time →Patching and support life over the years. |