This release is the first AREDN production release that omits the legacy OLSR protocol, and consequently the first release with the major number 4. That may sound scary, but if all your local nodes are on 3.25.5.0 or greater, they already speak Babel. That means a migration to this production release should pretty much be a non-event for your network.
If you are upgrading to 4.26.1.0 from a babel nightly build, you may see the following message:
BEWARE: Downgrading firmware WILL result in a broken or incomplete node configuration.
This can be safely ignored during this upgrade.
Major Features
- Babel only routing. OLSR is no longer available.
- OpenWRT 24.10.5 (https://openwrt.org/releases/24.10/notes-24.10.5)
- Support for some HaLow (802.11ah) 900 MHz radios
- Default NTP now aredn.pool.NTP.org
- Tunnel backup and restore to simplify node migration (https://docs.arednmesh.org/en/latest/arednGettingStarted/node_admin.html#tunnel-backup-restore)
- Support for user defined files in backups and upgrades (https://docs.arednmesh.org/en/latest/arednGettingStarted/node_admin.html#backup-configuration)
- Support for new app launcher in sidebar (https://docs.arednmesh.org/en/latest/arednHow-toGuides/app-launcher.html)
- Save AREDN node as a webapp.
- Bump the major release number to 4.
New Devices Supported
- Nanostation AC Loco
- Cudy TR1200
- Cudy TR3000
- HaLowLink 1
- Heltec HT-HD01
- Heltec HT-HD7608
- Alfa Tube-AHM
- Alfa Tube-AHM PoE
- Bhyve virtual machines
- VirtualBox virtual machines
Notes
There is still some instability with HaLow devices due to immature support for these radios in current Linux kernels. This manifests as occasional device restarts.
HaLow devices may sometimes require power cycling after upgrading.
The only thing I can think of they (the nightly and recent production) don't like the EdgeRouter-X settings... eth0 is WAN, eth1 is the AREDN node, eth2-4 are AREDN controlled LAN devices.
Can any tell me what the problem _could_ be?
Nick - VA7NIC
That device could be a non-supported device.
I have a PBE-M5-400 that loaded 4.26.1.0.
I did not attempt an RF, although.
73, Chuck
I couldn't establish tunnels, as it seems the outside didn't exist to it. From where it is mounted to provide 'it doesn't get banged around" access there is no RF, but we've built out our MESH some more since then, and the neighbor accross the alley has removed some trees so I may have an RF link again.
4.26.1.0 installs, doesn't say I have a non-supported device, it just has no clue of what the internet is, but I fall back to 3.25.10.0 and it works perfectly with various tunnels to places to ensure MESH access.
It says its an ath79/generic ubnt rocket-m-wx in the firmware window, is that part of the problem?
Should I wait or try sometime different.. as I mentioned before, the nightly builds since 3.25.10.0 do the same thing, install but no world to them.
Nick
Please state what device you have.
I am unfamiliar with a '400mil'.
73, Chuck
Hi, Nick:
IIRC, that firmware is what I used when I first purchased my pbe-m5-400.
Back in 2017-2020 it was common for there to be the same firmware
for the same model on different bands even.
It seems to me that Tim has been building specific firmware for each specific model.
I'll try a tunnel when I get home this afternoon.
73, Chuck
I tried again a couple hours ago, which still leads me to something external... I'll see what our group has to say on our video meeting this evening.
I've tried once more since my last attempt, and I get the same results: It runs but has no clue about the outside world as far as networking goes.
Nick
Nick
--Tim
--Tim
Firmware window says 3.25.10.0 (ath79/generic) ubnt (rocket-m-xw)
EdgeRouter-X (5 port) is setup just exactly how arednmesh.org wants for one wan, one node, and 3 lan ports.
You click on download firmware 4.26.1.0 and it does its thing, but upon reboot it has no internet.
Reuploading 3.25.10.0 has internet.
I have no current RF links, but I do have 2 tunnels, they both work under 3.25.10.0 but not 4.26.1.0. Our whole mesh is 3.25.10.0 so no older firmware is close to me.
A friend running the almost same setup is getting the same results as me...
Any other questions people have? Should I be running a different firmware that what aredn suggests in the download window?
Nick - VA7NIC
I feel that this discussion should be and should have been a new post.
I feel that this discussion is about what device you actually have and
what firmware you may try to load.
Please do not refer to firmware solely by release. e.g. 3.25.10.0.
Please use the firmware name.
e.g. aredn-4.26.1.0-ath79-generic-ubnt_powerbeam-m5-xw-squashfs-sysupgrade.bin
I recommend starting with a 'first boot' with firmware:
aredn-4.26.1.0-ath79-generic-ubnt_powerbeam-m5-xw-squashfs-factory.bin
In other words,
if you have a powerbeam-m5-xw that thinks it is a rocket,
do not let it choose what firmware to use to upgrade.
73, Chuck