I'm reading up on Ansible, and its ability to send commands to remote hosts looks like it might be useful to keep my fleet of nodes updated.
Can the AREDN firmware be updated using terminal commands?
I understand each node would need access to its correct upgrade binary, either through the arednmesh.org site or to a mesh file server that has the binary. Is anyone interested in looking into this with me? A friend of mine is an Ansible specialist and he's willing to assist.
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Use command line access to manually copy the sysupgrade.bin image to the /tmp directory on the node, then run the sysupgrade command manually from the command line on the node. Note that AREDN® nodes use port 2222 for secure copy and secure shell access.
upgrade-option:
-f <config> restore configuration from .tar.gz (file or url)
-i interactive mode
-c attempt to preserve all changed files in /etc/
-o attempt to preserve all changed files in /, except those
from packages but including changed confs.
-u skip from backup files that are equal to those in /rom
-n do not save configuration over reflash
-p do not attempt to restore the partition table after flash.
-k include in backup a list of current installed packages at
/etc/backup/installed_packages.txt
-T | --test
Verify image and config .tar.gz but do not actually flash.
-F | --force
Flash image even if image checks fail, this is dangerous!
-q less verbose
-v more verbose
-h | --help display this help
backup-command:
-b | --create-backup <file>
create .tar.gz of files specified in sysupgrade.conf
then exit. Does not flash an image. If file is '-',
i.e. stdout, verbosity is set to 0 (i.e. quiet).
-r | --restore-backup <file>
restore a .tar.gz created with sysupgrade -b
then exit. Does not flash an image. If file is '-',
the archive is read from stdin.
-l | --list-backup
list the files that would be backed up when calling
sysupgrade -b. Does not create a backup file.
simply omit the -n option
I think Steve copied the '1st install' procedure.
I followed that (1st install) procedure and my device (RB-SXT-5HPnD) rebooted into NOCALL on 192.168.1.1 channel 149/10.
I entered a new Node name and password. When it rebooted it came up with the original node name!
Omitting the '-n' ... the node returned in same state without changing node name or channel or bandwidth.
:-)
I hope this helps,
Chuck