AREDN highly recommends upgrading to AREDN security release v3.23.4.0
For more information see the Latest Docs page
AREDN highly recommends upgrading to AREDN security release v3.23.4.0
For more information see the Latest Docs page
Thanks to recent developments by Tim KN6PLV, we are introducing a new tool to help manage AREDN networks.
Nightly Build 1265 contains a number of improvements broadly called Link Quality Management. It’s designed to make the AREDN network more stable and improve the available bandwidth. Tests with these changes have shown improvements from modest to close to 200% in link throughput, tested end to end with iperf3.
Documentation is here
The AREDN team greatly appreciates all of the testing of the nightly builds as they roll out and introduce the new code base and features. We are paying close attention to your reports of successes and problems found.
Just as a reminder:
IMPORTANT NOTE: While AREDN encourages you to download, install and test the nightly builds and report any issues found, DO NOT install them in any node that doesn’t have easy access (e.g., towers, water tanks or mountain tops). By definition nightly builds are not to be considered production grade software.
Following their recent code production release, AREDN has embarked on an ambitious development plan. Here’s a basic overview of what is on their plate
The programming language for the user interface, services and many other functions is written in Perl. The Perl libraries are very large and AREDN has embarked upon a project to replace it with Lua, a much lighter weight programming language designed to run in embedded devices.
In steps, the team will update the “read-only” page to Lua:
Main, Mesh Status, etc.
Then the read-write pages will be updated:
Basic Setup
Port Forwarding DHCP and Services
Tunnel Server
Tunnel Client
Administration
Advanced
Configuration
And some others
Then the code base will be updated to OpenWRT 21.02.1. Besides code enhancements and security fixes, it brings in:
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.
When the size of the hostname and service advertisements exceeded the size of a single network packet, only IP addresses would be known. The...
#CallforCode 2019 five global finalists announced. Vote for your favorite #opensource tech solutions for natural disaster response and recovery. Pick the People's Choice Winner and get a chance to consult with a VC expert: ibm.biz/peoples-choice
Our resident network mapper and AREDN developer Eric KG6WXC just published a page describing his mapping program. His Automated Mesh Map allows hobbyists who have experience in Linux/Apache/SQL to collaborate while gaining metrics in their desired nodes. It has a become a “go to” tool for monitoring the status of the networks. Groups who start setting up their own AREDN Networks also get a copy of the map to monitor their progress.
You can get all the details on his page at SkySilk Cloud Services User Spotlight.
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer