You are here

Home » Forums » Development » General

Latest release 3.20.3.0

12 posts / 0 new
Log in or register to post comments
Last post
Sat, 03/28/2020 - 10:43
#1
w8erw
w8erw's picture
Latest release 3.20.3.0
I burned the midnight oil overnight and flashed several AREDN Nodes with the new firmware.  So far no issues and things appear to not only be running smoothly but a bit more consistently than with the blend of older versions that were in place.  Obviously it's early in the game, but I am quite please with this new release.   The nodes are a mixture of Ubiquiti, Mikrotik and Gl-iNET devices all of which took the upgrade cleanly and without any glitches.  That alone was enough to warrant my praise.  I trust everyone will see similar results.  Thanks team for the diligent and hard work that went into this effort.  We are quite fortunate to have you supporting the AREDN project providing all of us with an excellent concept and product that has unlimited possibilities. 
Top
Sat, 03/28/2020 - 12:04
WU2S
WU2S's picture
Thanks for installing on a variety of devices
Thanks for installing on a variety of devices. Since we support about 70 different devices and the AREDN team does not own examples of every one of them, it is very helpful to have people like you using the software and reporting your experiences. 
Please report any bugs or problems at our Github issues page.
Top
Sat, 03/28/2020 - 14:32
KG7GDB
Updates on Dropdown Menu on Admin Page?

We are upgrading many of our nodes today in Oregon.
After  5 reboots, my Mikrotik hAP ac node is back online with its tunnel client and iperfspeed packages updated successfully to 3.20.3.0
1) First thing we noticed, is that refresh of download firmware dropdown doesn't link to new firmware; only old versions.
-->Will there be a way to choose the latest stable release from the menu?
2) A refresh of packages reveals a new iperf3-v3.7 package needed to be installed. The old iperfspeed_0.5_all.ipk is still available on the documents page. It needed to be reinstalled, and then iperfspeed worked again. I had noticed iperfspeed was broken on the 1394 nightly build until the package was reinstalled.
-->Will iperfspeed be updated or added to the package download menu?

Thanks for all your work on the new release.
-Brett,
KG7GDB
Salem Oregon
See our live mesh map on https://willamettevalleymesh.net/map.html
 

Top
Sat, 03/28/2020 - 15:24
LA9UI
Latest release 3.20.3.0
I have just upgraded some nodes to 3.20.3.0. 5 NanoBridge 5G22, 2 NanoStation Loco M2 (XW) and 2 NanoBeam M5. All nodes but the first was updated via RF. All seems to be OK for the moment. By the way, we have about one and a half meter with snow, and still snowing in Tromsø, Norway. We have about 25 nodes operational here in Tromsø.
Top
Sat, 03/28/2020 - 16:12
(Reply to #4)
AE6XE
AE6XE's picture
LA9UI,  it's exciting to see
LA9UI,  it's exciting to see all the places around the world AREDN is being deployed to.  This is the first I know above the artic circle.  Would love to see your nodes on the AREDN map.   Glad all upgraded well.  Stay warm.

Joe AE6XE
Top
Sat, 04/11/2020 - 06:43
(Reply to #5)
LA9UI
Tromsø on the map
Tromsø, Norway is now on the map.
Top
Sat, 03/28/2020 - 16:00
K5DLQ
K5DLQ's picture
the "download firmware"

the "download firmware" option is somewhat challenging with this release and 2 architectures (ar71xx and ath79).
We will be working on enabling that for older devices to see the new firmware, but, it's alway possible to download the file and upload it.

UPDATE: most devices should have updated "download firmware" lists (exception is all of the TP-Link devices)

 

Top
Sat, 03/28/2020 - 17:03
kd5wma
Bullet M2 (XW)
Bullet M2 (XW)   seems to be listed twice on the download page for 3.20.3.0.   Are both software versions ok for Bullet M2 (XW)?    
Top
Sat, 03/28/2020 - 17:19
(Reply to #8)
K5DLQ
K5DLQ's picture
it's been corrected.   the
it's been corrected.   the ath79-bullet-m-xw firmware is correct
 
Top
Sat, 04/11/2020 - 14:31
NM7B
Oregon Washington county nodes updated
I updated the seven nodes in the Intel Corporation EOC mesh.  So far, so good.

Question: if I enable auto-distance (set to zero), how often does it reassess the best delay and adjust?  Right now I just left it at the previous fixed setting that I identified by running iperf and sliding the values up and down.  

73's,
Collier
NM7B
 
Top
Sat, 04/11/2020 - 14:56
(Reply to #10)
AE6XE
AE6XE's picture
The auto-distance is
The auto-distance is triggered in real time -- multiple times per second, depending on traffic, measuring ack responses.   Please note, buried in the help on the node, and forum, don't use this at short distances, a static setting would work a lot better -- under ~4 miles.   auto-distance works great with longer distance P2P links and improved over static settings.  It could be better/worse than static if many nodes on the channel, do iperf tests to optimize auto or static settings.

Joe AE6XE
Top
Sat, 04/11/2020 - 18:24
(Reply to #11)
NM7B
Thank you for the guidance!
Thank you for the guidance!  All of my primary nodes are within roughly four miles of each other, so I'll leave them at their static values.  However I do intend to add a separate node as a seed point to encourage other EOCs to our southeast to link into our mesh.  Those will be >4 miles away and would benefit from adaptive optimization.

Thank you for the excellent work, and 73's,
Collier
NM7B
 
Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer