slideshow 1 slideshow 2 slideshow 3 slideshow 4 slideshow 5 slideshow 6 slideshow 7 slideshow 8 slideshow 9 slideshow 10 slideshow 11

Alerts

There are NO alerts at this time. 

News


Release Candidate - Major changes and tests
 

The Release Candidate Process

 

The Release Candidate process starts with the release of nightly build 20261012-e3528941.

Subsequent nightly builds will be released when issues are fixed during this testing process and these will replace the current release candidate. The current release candidate is 20261012-e3528941. The process will continue until a build is considered stable. That will become the 4.26.X.0 release.

Please report all bugs using the usual process on GitHub. Functional bugs are the most important, cosmetic bugs are the least. You should not expect any major changes in functionality during this process. Please make sure you are running the latest release candidate before reporting an issue and please note the exact build number in your report.

If you are reporting a bug which appears to have been caused during the upgrade process, please make sure to include the version running before the upgrade was performed.

Before upgrading to an RC build, please backup your configuration. Apart from being a good idea, we might need this to aid debugging.
 

IPQ40xx Reboot Freeze 

In the 4.26.7.0 a Linux kernel bug prevents a small subset of Mikrotik IPQ40xx hardware from ever...

Read More
Updated date: Monday, October 12, 2026 - 19:52


Babel update for AREDN 4.26.7.0

Below is a link to download a new verison of Babel suitable for installing on AREDN 4.26.7.0. This new version includes a single bug fix to remove a potential maximum 4MB memory leak.

HOWEVER before you install this package please following the steps below to see if you should. In many cases this update will not effect how your node behaves or is not suitable for your device. There is no need to update a node with this fix if it is already working.

Should I install?

  1. Does you node have only 64M of memory? If you have more memory then this fix will do nothing. Yes you're wasting 4M of memory, but you node is under no memory pressure so there will be no operational difference. If you have more than 64M of memory don't install this.
  2. Is your node part of the ath79 family? If you don't know you can check the supported device list which includes this information (see https://github.com/aredn/aredn/blob/main/SUPPORTED_DEVICES.md). In fact there is only one 64M node which isn't - the "LDF 5 ac" - contact me if you have that node and need this fix as the package below is not for you. If your node isn't ath79 don't install this.
  3. Is your node running out of memory? If you're node...
Read More
Updated date: Wednesday, September 16, 2026 - 20:08


Important AREDN Patch

 

Recently the AREDN devs found a memory leak in the Babel source code. A ticket was opened with the upstream project, and a locally-derived patch implemented.

 

So - if you have a node with 64 MB of RAM that's moderately busy with Babel traffic, it'll run out of memory sooner or later (possibly sooner). If the node has 128 MB of RAM and isn't especially busy you might not ever see the node run out of RAM in between reboots.

 

What happens when a Linux machine runs out of RAM? Before that happens, the OOM (Out Of Memory)-killer kicks in. It tries to kill off processes that it deems least impactful, but rarely succeeds. So you end up with a misbehaving or non-functional node, only restored by rebooting.

 

So, consider updating your nodes to the latest nightly build, in order to incorporate the patch for this memory leak.

Updated date: Saturday, September 12, 2026 - 10:01


Upcoming Nightly Builds


The next series of AREDN nightly builds contain significant changes to how we manage a device’s network. This includes supporting the mesh on multiple radios at the same time (a long requested feature) and removing the need to provide IP addresses for tunnels and xlinks, making the creation of these much simpler.

These changes are not backward compatible, so once a new nightly is installed you cannot restore to 4.26.7.0 without doing a fresh install, and then using a previously created backup

So - do not upgrade to a nightly build unless you have already backed it up, and have physical access in case of issues.

The AREDN Dev team

Updated date: Wednesday, July 15, 2026 - 19:03

Pages

Announcements


NG1P April 2022 Wireless Mesh Using AREDN

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.


AE6XE on YouTube Hamfest 23 May 2020

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