* This release is incompatible with MeshChat 2.9 or earlier.
* GL.iNet GL-B1300 does not support negative channels on the 2.4 GHz band.
## Fixes and Improvements
* Updated to latest OpenWRT 23.05.3
* Fixed wifi scan for Ubiquiti AC devices
* Now ignore tracker entries without IP addresses
* Limit buffer size of IPerf3 test to 16K
* Improved IPerf3 api reliability
* New supernodes will no longer have access to legacy tunnels
* Legacy tunnels will be removed from supernodes in the next prod release
* NOTE: in the distant future, legacy tunnels will be completely removed. Migrate to Wireguard tunnels now and avoid the rush :-) They’re way better anyway.
* Collapsed QEMU and VMWARE VM hardware into two basic types
* Validated network override configs
* Now hide long time idle neighbors
* Fixed PowerBeam 5AC 400 name
* Labeled Wireguard tunnels in LQM
* Added support for dynamic number of Ethernet ports on VMs
* Added retry for failed firmware version downloads
* Improved the messaging when failing to retrieve firmware versions
* Fixed tunnel net display truncation on some browsers
* Made sure the node names we use for tunnels are always uppercase
* Switched Nanobeam 2AC to DD-WRT firmware (doesn’t function on 10MHz otherwise)
* Fix display of NTP update when it changes
* Add rev DNS lookup for supernode tunnels
* Make sure switching wifi modes forces a reboot.
* Fixed wan client/no encryption mode
* Fixed xlink monitoring by LQM
* Removed fixed tunnel limits
* Improve VLAN selection in advanced networking
* Fixed all x86 mac addresses
* For x86 devices, make all the bridge mac addresses unique. Gives more flexibility when virtualized.
* Added extra protection for bad OLSR info
* Fixed bug in route truncation in low memory situations
* Now refresh browser cursor on each LQM iteration
* Ports Page:
* Added Advanced DHCP Options selector on Port Forwarding, DHCP, and Services page
* Front Page:
* Now show antenna information on the front page
* Internal antenna info is automatically shown
* External antenna info may be added on the Basic Setup page
* Added frequency range on front page to help detection of overlapping channels
* Basic Status page:
* Added support for azimuth, elevation, height above ground and external antenna type
* Note – if the node has azimuth information set, the bearing of its antenna will be displayed on the mesh map by rotation of the node’s pin on the map ( https://arednmap.xojs.org ).
* Mesh display improvements:
* Added xlink display to remote nodes
* Fixed LQ display of weighted local links
* Fixed NLQ display of weighted links (using the LQ weight ... and assume its symmetrical)
* Now sort the remote node list by ETX, then alphabetically
* Fixed clearing the mesh search field
* Another attempt to deal with occasional missing remote hosts
* Added watchdog support. The watchdog monitors three things:
* A set of important system daemons.
* A set of pingable ip addresses.
* A time the node should reboot everyday.
* Countdown timers for reboots and firmware updates.
* Reboot pages will now refresh once the node is ready rather than after a fixed timeout.
* Increased wifi retries for noisy links
* Auto mesh page updates no longer persist
* Auto scan page updates no longer persist
* Eliminate duplicate past neighbors
* Support default /metrics path for Prometheus
* Fix various color problems on alternate display styles
* Add green on black style
* Half olsrd maintenance traffic rate
* Fix clashing IP address on devices with the same mac address ethernet and wifi hardware
* Fix Bad Gateway when rebooting from tunnel pages
* Add CIDR network to Xlinks
* Provide better xlink information in sysinfo.json
* Include tunnel information (redacted) in support data dumps
* Fix badly escaped character in tunnel gmail emails
* Improve speed and relevance of search on mesh page
"mesh of meshes". With this release your localnode will automatically detect a nearby
supernode, and will show a new button on the Mesh Status page, labeled "Cloud Mesh".
Clicking on that button will take you to the Mesh Status page of that supernode and show you
all the nodes and services on the Cloud Mesh. You can navigate to any of them as though they
were on your local mesh.
The URL for the supernode map is currently https://arednmap.xojs.org/ Clicking on any of the
nodes in the upper-right-hand corner of the map will filter all other nodes out, showing only the
types selected.
* Remember and reinstall packages after firmware upgrade (AFTER this version is installed)
* Simplified search tool
* Added LZ77 decompression for Mikrotik firmware, which is now using a different compression method
* Cron
* Now run cron.boot tasks earlier
* Changed pollrate default to one hour
* Added installable cron package for people who need more functionality
* Improved dual radio configuration support in hAPs
* Added support for wildcard DNS subdomains
* Now using frequency list for scan. Some hardware didn’t scan all the frequencies we want by default. (Not a fix for the scan issue seen on some AC devices.)
* Set tunnel weight to 1 and provided UI to change it. With this change, if there are both RF and tunnel links to a destination, the tunnel value can be set high (relatively poor). In that way traffic will only flow over the tunnel if the RF link goes down. This provides an effective method for implementing backup links.
* Bumped the allowed Ubiquiti version numbers to support AREDN® installation on newer LiteBeam 5ACs. (Probably all new Ubiquiti devices but currently only tested on Litebeams).
There have been over 70 nightly releases of the AREDN® codebase since the last production release in April of 2023. Here are the highlights of the latest production release:
* Upgraded to OpenWRT 22.03.3; the latest release of OpenWRT with many security and bug fixes.
* Upgraded to Linux kernel 5.10.161
**IMPORTANT NOTE!**
Because of changes in the way OpenWRT names devices, this upgrade is not simple to revert without reinstalling your node as if you just took it out of the box.
## New Devices
* Ubiquiti [1]
* LiteAP 5 AC
* LiteBeam AC5 Gen2
* NanoBeam AC 5 (WA)
* NanoBeam AC 5 (XC)
* NanoBeam AC 5 Gen 2 (WA)
* NanoBeam AC 5 Gen 2 (XC)
* NanoStation AC 5
* PowerBeam AC 5 Gen2
* PowerBeam AC 5 400
* PowerBeam AC 5 500
* Rocket 5 AC Lite
* Mikrotik
* hAP ac2
* hAP ac3
* SXTsq 5 ac
* LHG 5 ac
* LHG XL 5 ac
* LDF 5
* mANTBox 15s
* mANTBox 19s
* TPLink
* CPE710 v1.0
* GL.iNet
* Shadow (128MB NAND)
* Slate
* Mudi
For a full list of supported products, see the list [here](http://downloads.arednmesh.org/snapshots/SUPPORTED_DEVICES.md).
1.**Important** - the initial factory installation instructions for Ubiquiti 802.11 ac products are new. They can be found in the AREDN® Online Documentation [here](http://docs.arednmesh.org/en/latest/arednGettingStarted/installing_firmware.html#ubiquiti-802-11ac-first-install-process).
2. The 802.11ac products offer noticeable advantages over the legacy 802.11n devices. If you’re contemplating a new deployment or just looking for better performance, consider an 802.11ac device. Here’s [a list of recommended devices](https://www.arednmesh.org/content/device-migration-suggestions) for migrations.
3. Over and above neighbor status states of pending, active and idle, new states of hidden and exposed have been added. Because the nodes talk amongst themselves, your node knows which of its neighbor nodes are nearby but hidden from it. This can be useful for network management. Exposed nodes are nodes that a node can see, but will block it from transmitting to other neighbors when they are transmitting. It's a bit complex - see the 'exposed node problem' in Wikipedia for more detail The AREDN® team hopes to use these parameters in the future to reduce channel congestion.
* Now automatically enable RTS (Ready To Send) when hidden nodes detected
* Fixed IBSS (Independent Basic Service Set) problem on 2.4GHz
* Enabled negative channels for 2.4 GHz 802.11ac devices
* Fixed negative channels not beaconing.
* Fixed power offsets on various devices
* Fixed fccid beacon
* Fixed -ac coverage calculation in driver.
* Resolve unresponsive node problems with Mikrotik AC devices
* Now ignore non-routable when calculating hidden nodes
* Network performance improvements
* Added a maximum timeout for service checks
* Provided a timeout on the iperf3 client
* iperf3: Improve error reporting when server is busy/disabled
* Set up to refresh LQM’s hostnames periodically
* Made the default country HX (HAM)Now handle missing IP address and create more general RF/DTD identification
* Validate state of services over a period of time before disabling advertisements
* Force dnsmasq to update itself if no network changes for > 60 secs
* Fixed idle tunnel quality check
* Fixed WAN VLAN detection on hAP
* Fixed the netmask on the br-nomesh device (for when RF mesh is disabled)
* A node with a single RF link can’t have any exposed nodes - corrected
* Filtered out non-routable ARP entries which confuse LQM
* Don't let services use hostnames which are not propagated.
* Block DHCP server traffic from ever going to the WAN interface
* Reworked the DTD blocking detection
* Fix occasional LQM nil error
* Eliminate false network rejoins using LQM information
* Force badly associated stations to reassociate.
* Node management improvements
* Improved the quality of the scan output
* Improved idle tunnel quality measurement
* Provided better error feedback when upgrades fail
* Tagged devices which must be reinstalled. (The NAND layout for a few Mikrotik devices has changed sufficiently that they cannot be easily upgraded and must be reinstalled from scratch.)
* Now gather statistics about RF links
* Established a more consistent way to provide interface mac address in overrides
* Support forced upgrades
* Move the unconfigured setup earlier
* Handle system upgrade files of type “nand-sysupgrade”
* Remove WAN Wifi Client key lower limit
* Improve AP band selection
* Add extended channels to LAN AP list
* Fixed PowerBridge M upgrade
* Fixed AirRouter port identification
* Made sure we look for packages with the correct architecture
* Fixed AR150 port settings
* Fixed Mikrotik boot loader to avoid boot lockup problem
* Improved firmware failure error recovery
* Stop RETURN from refreshing the mesh page
* Fixed support for Mikrotik LHGG-5acd-xl
* Fixed upgrade compatibility for nanobeam m5 19
* Fixed AP mode selection when turning mesh back on.
* More fixes for AP mode
* Fixed firewall rule checking for existing drop rules
* Fixed monitors not detecting non-mesh mode
* Created new network configuration code
* Miscellaneous
* Merged openwrt release 22.03.3
* Updated firmware selector on web page
* Made sure we never pass ‘nil’ to the json parser
* Fixed xlink firewall rule inserted incorrectly
* Removed a firmware blocker we no longer need
* Added a note about the USB150 & AR150 devices
* Added "hidden" and "exposed" node statuses to help file
* Re-enabled the kmod-rtc-ds1307 package
* Some initramfs cleanup
* Generalized node-setup variable expansion
* Removed firewall counters except for specific ports
* Now use luci’s urldecode_params to handle query strings
* Added “tiny build” notes
* Set PowerBeam-M2-400 to stable status
* Fixed service alignments on web page
* Add SKUs to Supported Devices doc
* Cleaned up Supported Devices doc
* Split the various Mikrotik radios into their individual variants
* Clarified the Mikrotik LHG 2nd firmware versions
* Validate Bullet M5 build
* More upgrade compatibility
* Ath9k driver - no error accounting - added
* Fixed the bandwidth reporting for ath10k devices
Since version 3.22.8.0 was released in August, over 50 nightly builds have been released. So the dev team decided that it was time for another production release. While many of them were small tweaks, some were significant. Here’s a summary:
## UI (web page) updates.
Many updates were made to the UI (web pages) to increase usability and provide additional information. Some highlights:
* Added NTP update period to basic setup page - can now choose between daily and hourly updates
* Now display host totals rather than OLSR totals
* Added search capabilities to the Mesh Status page
* Grouped Mesh RF info if WiFi is enabled
* Both types of gateways on Status page now displayed
* Added a warning when attempting to add extra packages to 32 MB nodes
* Added help link to pages missing it.
* Changed support link to button
* Updated help file for new Advanced Config format
* Simplified Advanced Config display
* Added units to Setup and Advanced Config pages
## Miscellaneous fixes and updates
* Optionally include static routes (and preserve them across upgrades)
* Added support for extra network links to OLSR
* Included wireguard packages in the repo
* Fixed recoverymode script (didn't work correctly)
* Stopped a node from including itself in its LQM neighbors
* Fixed bad match for NAT DHCP addresses.
* Added a wifi scan trigger for when the "nodes detected" count becomes zero (resets wifi)
* Added a snapshot of hostnames after OLSR updates so we have a consistent copy to display on Mesh Status page
* Advertised services:
* Determination logic updated
* Added more 3XX redirects + 401 authentication
* If redirect ends at an https link, assume it is valid
The AREDN® development team has shifted into high gear with this third release of 2022! This production release adds the many fixes and enhancements made since 3.22.6.0
* Dealt with LAN on AR300M always having the same MAC address.
* Fixed default DHCP limits in NAT mode if fields are blank.
* Fixed a "do not propagate" issue when reserving DHCP names.
* Fixed tactical names.
* Fully validate node and tactical names; give better messages when invalid.
* Prevent <and> from being used in service names.
* Correct map update claiming success when it actually fails.
* Added device definition for Ubiquiti PBE M5 300-ISO.
* Some Ubiquiti Powerbeams: keep 100MB as the only port speed, but let the port auto-negotiate with the switch to fix throughput issues.
* Fixed display of unknown radio models.
## Enhancements
* Added a service alert icon.
* Adjusted the Administration page display. (advanced WAN moved to AdvConfig page)
* Added changeable WAN VLAN support to the Mikrotik hAP and AR300M.
* Allowed display of longer filenames (wider field).
* Now run an hourly check on published service and “unpublish” any which aren’t really available. Re-enabled services will be republished automatically.
* Added a visual indicator to show when a service is not being published.
* Made “Keep Settings” more prominent.
* Renamed Support Data file extension from tgz to gz (to allow them to be easily added to a forum post and/or github issues).
* Allow zero length WAN WiFi client passphrases.
* Allow LQM auto-distance to be overridden.
* Further improvements in LQM.
* Password visibility toggles on setup page.
* Added connection status feedback when using WAN WiFi.
* Status page now shows if you’re using wired or WiFi WAN.
* Updated the HTML Help file to reflect these changes.
Since the last production release, there have been 136 separate ‘pull requests’ in the AREDN® github repository. Those requests pulled these significant improvements and new features into the AREDN® software:
1. The conversion from Perl programming to Lua is complete - the result is a significantly smaller, somewhat faster, code base.
2. Due to the recovered space in the image, tunnels are now always installed, so nothing needs to be done with them during future upgrades.
3. After this upgrade, future upgrades should be much more reliable, especially on low memory devices.
4. Tunnels will be prevented from accidentally connecting over the mesh.
Tunnels normally connect via the WAN interface, that being the point of the things. However, if the WAN interface on a node goes down for some reason (the tunnel server/client Internet fails) the node will select a new way to talk to the Internet by first routing over the Mesh. When this happens, tunnels could end up being routed partially over the mesh, which is bad because tunnels are also part of the mesh. So, we now prevent this by default by adding a firewall rule.
5. You can now adjust the poll rate for alerts. AREDN® alerts and local alerts (those yellow banner things you see sometimes) were polled twice a day. This is now configurable.
6. There is now a 60-second timeout when tunnel connections are interrupted.
Node tunnels run over TCP/IP so they guarantee that what is sent is what will be received. This is all fine when things are running reliably, but if a connected tunnel fails for a bit, but then recovers, this guarantee means very old, pending traffic will still be delivered. In AREDN’s case, this traffic is not useful to the user, and for OLSR it is positively dangerous to deliver ancient routing information. This is all low level protocol stuff and there will be no visible effects to users.
7. Nodes which are only connected via the WAN port and tunnels (no Wifi, no LAN) can cause some configuration problems because AREDN® really wants either the LAN port to be connected or the WiFI to be enabled. We made some changes, so this is no longer a requirement. Thanks to K1KY, who has some unusual setups, for finding this.
12. Added the capability of loading firmware updates "locally" after copying them to the node via SCP. This is useful if you’re trying to update a distant node over marginal links. Information on how to use it is in the AREDN® online docs, here.
First, it drops links to neighbors which won't work well. Links are dropped that don't have good SNR, are too far away, or have low quality (forcing retransmissions).
Second, it uses the distance to the remaining links to optimize the radio which improves the bandwidth. This mechanism replaces the older ‘auto-distance’ system which was often confused by distant nodes with which it could barely communicate.
Many LQM parameters are capable of being modified to allow for local network circumstances. There’s documentation on LQM in both the node help file and in the AREDN® on-line docs.
**NOTE 1:** LQM is turned off by default, unless it was previously enabled in a nightly build.
**NOTE 2:** Latitude and longitude need to be configured in order for LQM to work properly.
**IMPORTANT NOTE:** If you’re running MeshChat and/or iPerfSpeed, after this upgrade you’ll need to install compatible versions of them (but note that with the built-in throughput test you may no longer need iPerfSpeed). URLs for those versions:
1. The AREDN® simplified firmware filename standard has been changed to the default OpenWRT convention to leverage data files created at build time for future automation of firmware selection.
When installing this firmware release, from prior firmware versions, you may get an error message similar to
“This filename is NOT appropriate for this device.“
“This device expects a file such as: aredn-3.22.1.0-main-ef2d605-ubnt-nano-m-xw-.*sysupgrade.bin”
“Click OK to continue if you are CERTAIN that the file is correct”
Ensure that you are loading the correct file by referring to the downloads page, then safely ignore the warning. Once this release is loaded, this error message will never occur again.
2. When the size of the hostname and service advertisements exceeded the size of a single network packet, only IP addresses would be known. The advertised services and hostname would not propagate to other nodes on the network. The OLSR routing protocol was changed to fix this.
3. The OLSR scalability failure, commonly called “OLSR storms”, has been fixed. Large networks with hundreds of nodes would experience cycles of routing disruption, making the network unusable.
4. SNR history may be missing neighbor node names – fixed.
5. When defining a local location of packages in Advanced Configuration, there was no way to change the location of some packages obtained from the upstream Freifunk group. The Advanced Configuration page now has a row to define this local location.
6. Performance improvements were made to the Mesh Status page based on results from the large scale stress test on Oct 31, 2021.
7. Local alerts as configured on the Advanced Configuration page can now have zones which allow a mesh user to subscribe to alert messages affecting a specific locale.
8. The allowed number of tunnel connections is now configurable on the Advanced Configuration page.
9. There are numerous API updates.
# 3.21.4.0
This release contains, among other things the following changes and fixes:
* Fix spike to zero in SNR Chart #90 (ab7pa)
* Execute Button Description #86 (ab7pa)
* Add Rocket XM ar71xx image to support older models with USB port #83 (ae6xe)
* Fix tunnel server clients accidentally limited to 9 #82 (pmilazzo)
* Add “none” type advanced config options to simplify the UI #81 (dman776)
* Update banner #80 (dman776)
* update login banner #79 (dman776)
* Add mesh gateway setting to sysinfo.json #77 (dman776)
The AREDN® team is pleased to announce the general availability of the latest stable release of AREDN® firmware. We now fully support 70+ devices from four manufacturers. This diversity of supported equipment enables hams to choose the right gear for a given situation and budget.
The AREDN® team is pleased to announce the general availability of the latest stable release of AREDN® firmware. We now fully support 70+ devices from four manufacturers. This diversity of supported equipment enables hams to choose the right gear for a given situation and budget.
AREDN® firmware is now based on the most recent stable version of OpenWRT19.07.2 which was released in March 2020. This improvement is significant in that it enables AREDN® firmware to benefit from the many bug fixes, security improvements and feature enhancements provided by OpenWRT developers from around the world.
The latest AREDN® firmware contains features inherited from the newest OpenWRT upstream release (19.07.2). One important change is the inclusion of a new target (architecture) for the firmware, labelled “ath79”, which is the successor to the existing “ar71xx” targets. OpenWRT explains that their main goal for this target 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. As not all supported devices have been migrated to the new “ath79” target, AREDN® continues to build firmware for both targets. You may notice that the AREDN® download page has firmware for these two targets, and you should select the latest image based on the type of hardware (and the recommended target) on which it is to be installed.
Several devices are now shaded in light green to indicate that they are no longer recommended for AREDN® firmware, primarily due to their low computing resources (memory/storage).
OLSR is the capability in AREDN® that exchanges IP Addresses, Hostnames, and figures how to route packets across the mesh network. There continues to be an intermittent defect when OLSR starts as a device is powering up. OLSR fails to propagate or may miss receiving some hostname information. A one-time restart of OLSR will resolve the situation. This option can be found in Advanced Configuration settings--it doesn’t save a setting per se, rather restarts OLSR without rebooting the device.
* IP Address is showing in Mesh Status: go to the IP Address’s node and restart OLSR
* “Dtdlink” or “mid” is showing in a host name: go to those hosts and restart OLSR
* Others can access a device by the hostname, but I can’t: restart OLSR on my device
### PBE 400/400-ISO/620 degraded throughput over ethernet port
These Uniquiti PBE devices have a gigabit Ethernet port that does not handshake correctly with some switches. The device’s Ethernet port is locked to a 100mbps rate at Full-Duplex (still sufficient for the max rates generally achieved over RF). This made the port always functional, but for some switches the performance may be severely degraded. It is recommended to lock the rate on all switches this devices is connected to at the same 100mbps rate at Full-Duplex. Check your switch’s port statistics to determine if there are TX or RX packet errors. Alternatively, an iperf test from the node to another node on the same switch will identify if there is any performance degradation.
### Upgrading Firmware Images
1) 32M RAM devices continue to be at the limit of available memory. This means that doing a sysupgrade to load new firmware may take many tries to succeed. Don't use these devices at hard to reach tower sites! The sysupgrade process needs close to 10M of memory to succeed.
**Tips to get it to work:**
1) fresh reboot and very quickly do the upgrade (recommended for all devices, particular if at a tower site)
2) disable mesh RF and any use of wireless, reboot before sysupgrade
3) disable or uninstall any packages that are running, e.g. meshchat
4) as an almost last resort, scp the .bin image to /tmp on the node and from the command line type "sysupgrade -n <.binfilename>" (does not save settings)
5) as the last resort, tftp to load the factory image (does not save settings)
2) Do not count on being able to sysupgrade to return back to older AREDN® images, when upgrading to ‘ath79’ target images. It might work, it might not based on if model names were cleaned up and changed moving to ath79. The older images may not be recognized on the newer target images. Do a tftp process instead.
