There are NO alerts at this time.
There are NO alerts at this time.
AREDN®, as we’ve come to know it, is 11 years old. In that time it has come a long way, supporting a wide variety of devices, a host of radio bands, and has been deployed across the world. The UI has evolved, tunnels have been added, bandwidth and throughput have increased, and more features and services can be supported. The one constant in all this has been how AREDN® manages the network, using a protocol called Optimized Link State Routing - OLSR. Unfortunately as networks have grown, this protocol has buckled, and sometimes broken, under the strain, as OLSR was never designed for the size or variety of the networks we have. This year we added a new modern network protocol - Babel (see the How-To in the online documentation for more information). The goal has been to replace OLSR after a period of testing and migration, and we imagined it might take years to successfully transition from one protocol to the other. Instead, we have been blown away by how our community has embraced and requested this change. As of this writing, almost 80% of nodes worldwide are running firmware which uses the Babel protocol.
With this in mind, we have decided to move more quickly...
Nightly build 20250723 has been designated as the Release Candidate for the next AREDN production release. If nothing weird happens, the next production release will be around August 6th.
The recent nightly builds have been very stable. The AREDN team encourages you to wring them out and see if you can break them :-)
Enjoy!
It figures... After several months of testing, a bug in the Babel implementation surfaced - naturally after a product release. Somewhat randomly and rarely, after a reboot or upgrade, the Babel connection between two nodes will not operate correctly. Symptoms are lack of connectivity with Babel nodes, usually in one direction rather than both. If you're experiencing this, open up the panel on a Local or Neighborhood node. The issue is evidenced by the Babel Metric in the lower right having a value of -1.
Restarting Babel at either end of the connection should resolve it, as it appears to be a boot-up timing issue. Rebooting one of the nodes is the easiest way to do this. But consider updating to production release 3.25.5.1 which will resolve the issue.
Bill Richardson NG1P presents his views on organizing an AREDN mesh network in Maine at the ARRL Convention in Lewiston, Maine on April 1 and 2, 2022.
The presentation is here.
Joe AE6XE described typical AREDN deployment scenarios with Ham Radio 2.0 host Jason KC5HWB. He offered advice on how to get started and choosing suitable devices.
His presentation slide deck is here.
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer