Please read UPGRADE.txt and changes-0.7 before you start.
If you are using mISDN with PCI cards please also read this.
(new after 0.6.2)
Most normal users should use this process. You can upgrade now from the web interface OR from the CLI
If a new version is found, you'll see a message at the top of the page after a short delay.
Next, change the dropdown to “upgrade with new”, check the confirm checkbox, then click the firmware button. The new firmware will be downloaded. At that point, you will be prompted to reboot to use the new firmware.
If you used the firewall in the web GUI in 0.6, you will need to upgrade Arno's firewall:
On the command line, the commands are similar:
upgrade-run-image check http://mirror.astlinux.org/firmware
upgrade-run-image upgrade http://mirror.astlinux.org/firmware
or the URL from above for Asterisk 1.8.
If you used the firewall in the web GUI in 0.6, you will need to upgrade Arno's firewall:
upgrade-arno-firewall upgrade
or hand edit, copy and patch the /mnt/kd/arno-iptables-firewall/
directory$ vi /mnt/kd/rc.conf
$ gen-rc-conf
$ arno-iptables-firewall restart
(Not required for most users)
Follow these steps to upgrade an existing Astlinux 0.5 or later installation. You no longer need to transfer a completely new image using dd or physdiskwrite. You don't even need to remove the media from your existing AstLinux device! With AstLinux running, perform the following steps.
mount -o remount,rw /oldroot/cdrom
cd astlinux-0.6.0-<ARCH>; cp * /oldroot/cdrom/os
(if downloaded and decompressed on your client PC, you'll want to use a tool to scp the files to the AstLinux device.
NOTE: AstLinux supports retaining multiple versions in the 'os
' directory. To determine which revision is booted, a 'ver
' file is used. This ver
file should contain a single line that lists the version to boot (for example: astlinux-0.6.1) If no ver
file is present, the boot loader will load the 'highest revision', determined alphabetically (so 0.6-2011 would be newer than 0.6.2). So be careful if upgrading from an SVN version!
If your existing 0.6 installation has NICs of more than one type (different chipsets/drivers), there is the possibility that the numbering of these NICs under 0.6 (eg eth0
, eth1
, etc) will change once upgraded to 0.7. Please bear this in mind, especially if attempting a remote upgrade. For an explanation, see Changing Network Hardware.
You may also need to change the Active Channels, Voicemail and Reload Asterisk Commands, in the Prefs tab:
core show channels
voicemail show users
module reload app_voicemail.so
module reload