Downloading AREDN® Firmware
Current Stable Releases
Once you have selected and obtained a device, the next step is to choose the matching AREDN® firmware image for that specific device. The AREDN download page displays the most current firmware releases for every supported device.
Locate your device model/version in the left column. Most manufacturers print the hardware version on the product package label. In some cases, though, you may need to start the device using the manufacturer’s pre-installed firmware and navigate to the system information page to determine the hardware version.
There are two types of firmware images: one for the first-time replacement of the manufacturer’s firmware, and the other for upgrades of nodes that are already running AREDN® firmware.
If you are loading AREDN® firmware on TP-LINK or Ubuquiti devices for the first time you must download the factory firmware from the middle column. For Mikrotik devices you must download both the factory and sysupgrade images. For GL.iNet devices you must download the sysupgrade image from the righthand column.
If you are already running AREDN® firmware on the node then you will choose the sysupgrade firmware from the righthand column, and you will use the AREDN® web interface to perform the firmware upgrade.
Once you have selected the correct firmware image for your device, click the link to download the image file to your local computer. Make a note of the download location on your computer, since you will need to use that image to install the AREDN® firmware on your device.
- Features Inherited from OpenWRT for New Architectures
The latest AREDN® firmware contains features which are inherited from the newest OpenWRT upstream releases. The OpenWRT *Release Notes* describe these new features.
One important change is the inclusion of a new target architecture for the firmware, labelled “ath79”, which is the successor to the existing “ar71xx” target. The OpenWRT team explains the new target here: ath79. Their main goal is to bring the code into a form that will allow all devices to run a standard unpatched Linux kernel. This will greatly reduce the amount of customization required and will streamline the firmware development process.
Since not all supported devices have been migrated to the new “ath79” target, AREDN® continues to build firmware for both targets as needed. You should select the latest recommended target image based on the type of hardware on which it will be installed. Refer to the latest Firmware Notes in order to ensure you have the correct firmware image for your specific device.
Nightly Build Firmware
Nightly Build firmware contains the latest bug fixes, features, and support for the newest devices being added to the Supported Platform Matrix. It allows the wider mesh community to test new code before it is included in a formal code release. The Nightly Build is considered more experimental or cutting-edge and may not be suitable for production nodes. However, if you are having a specific issue that has been addressed in newly developed code, or if you are loading AREDN® firmware onto a device that has just been added, then it might make sense to install the nightly build firmware.
To download the Nightly Build, navigate to the Software > Nightly Builds link on the AREDN® website. Nightly Build filenames are prefixed with aredn-XXXX-yyyyyyy, where XXXX identifies the build number and yyyyyyy is a unique software commit identifier. You will find the most recent README file, a cumulative list of the changes included in the build, and a link to download the firmware. As explained above, select the correct target architecture for the device you will be flashing. To return your device to the current stable release, download the correct Stable Release firmware and reflash your device.
Be aware that when a new nightly build becomes available, any older builds automatically become obsolete. If you want to install add-on packages for nodes running a nightly build, understand that specific packages will not be available for an older build if a newer build has superseded it. Be sure to upgrade to the current nightly build before installing packages. Nightly build firmware contains the cumulative changes that have gone before, so review the Changelog to determine which features are included in the build.