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.
Thank you for answering my inquiry.
My neighbor is "3" hops away from my RocketDish (which is also my LAN router). My dish links to a PowerBeam (30 feet) via RF. That PowerBeam is DTD to another RocketDish on a different RF channel. That RocketDish links to my neighbor's NanoBridge via RF. (The first three radios are mine, K9LMR).
I upgraded my radios to 4.26.1.0 and lost the connection to my neighbor who is stuck at 3.21.4.0
I backed my RocketDish (RF link to the neighbor) to 3.25.10.0 but I couldn't achieve a connection to the neighbor.
After I backed all three of my radios to 3.25.10.0, I am once again connected.
Is this normal?
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
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