There are NO alerts at this time.
There are NO alerts at this time.
Nightly build 2017 is based on the latest OpenWRT release, version 22.03.2. (The current AREDN production release is based on OpenWRT 19.07 from January 2020).
There are significant changes in this nightly build:
All devices have been moved to the ath79 device tree (no more ar71xx).
The ipq40xx device tree has been added.
Each device now has its own image file.
Some filenames have been changed.
As a result devices need to be tested carefully, at least initially.
The most current status on nightly builds can be found in the README file here:
http://downloads.arednmesh.org/snapshots/readme.md
While this release has been tested on more than 90% of device types active on AREDN networks, it could not be tested on everything and support for some devices is either untested or not readily available. If you need a nightly build that’s missing please let us know and we will add it if possible (but you will need to provide hardware for development and testing).
This...
Read MoreThe 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
AREDN production release 3.22.6.0 is now available. This is the release you've been looking for :-)
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....
If you plan to take advantage of the extended Amazon Prime Day on July 15 and 16, please consider supporting the AREDN Project with your purchases.
Simply shop at smile.amazon.com/ch/83-0671991 and AmazonSmile donates to Amateur Radio Emergency Data Network Inc
AREDN developers Joe Ayers AE6XE and Darryl Quinn K5DLQ were interviewed by Daniel Krook, the Chief Technology Officer for the Call for Code Global Initiative and the IBM Code and Response.
This fascinating discussion focuses on questions and ideas that will interest software developers and participants in the 2019 Call for Code Challenge.
You can find the video on the IBM Developer channel on Twitch.
AREDN is a 2019 Call for Code Program Supporter. Join Call for Code in building solutions to improve disaster relief efforts and a chance to win $200,000.
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer