There are NO alerts at this time.
There are NO alerts at this time.
Starting May 6, 2023 nightly builds will have a filename format that includes the build date rather than the job ID.
Like this: aredn-20230506-xxxxxx.bin
There have been over 140 nightly releases of the AREDN codebase since the last production release in December 2022. Here are the highlights:
IMPORTANT NOTE!
Because of changes in the way OpenWRT names devices, this upgrade is not simple to revert without reinstalling your node as if you just took it out of the box.
Ubiquiti[1]
AREDN at SCALE 2023
Thanks to the great AREDN team led by Orv W6BI, we had a significant presence at this year's SCALE event.
Important note - 802.11ac equipment will not function completely properly without nightly build 2316 or later
Enhancements
Added Mikrotik QRT5 support
Added Ubiquiti Nanobeam ac gen1 xc support
Established a more consistent way to provide interface mac address in overrides
Provided a timeout on the iperf client
Now gather statistics about RF links
Updated firmware selector on web page
Set up to refresh LQM’s hostnames periodically
Made iperf3 improvements
Now ignore non-routable when calculating hidden nodes
Now handle missing IP and created more general RF/DTD identification
Now automatically enable RTS when hidden nodes detected
Bug fixes
Fixed "coverage" (distance) calculation in 802.11ac driver.
(not working correctly for 5 & 10 MHz bandwidths; disabled for now)
Fixed AirRouter port identification
Made sure we never pass ‘nil’ to the json parser
Made sure we look for packages with the correct architecture
Fixed an xlink firewall rule inserted incorrectly
Fixed the netmask on the br-nomesh device (for when RF mesh is disabled)
A node with a single RF link cant have any exposed nodes - corrected
Fixed AR150 port settings
Fixed power offsets on various devices
Fixed...
It is US National Hurricane Preparedness Week! Are you prepared for this year’s hurricane season? Are you ready to assist others by providing high-speed communications when the commercial facilities are not available?
As a 2019 Call for Code Program Supporter, the AREDN team asks you to watch how Call for Code 2018 winner Project Owl piloted their mesh network solution to help communities in Puerto Rico https://ibm.co/2UUv1Ge
We plan to host a discussion on deploying an AREDN mesh network in Puerto Rico during Hamvention in our booth #1001. Please join us and contribute your ideas.
There is another way to help in creating a cleaner, safer and healthier environment for the worst hit communities and a chance to win $200,000 USD. Enter the 2019 Call for Code challenge https://ibm.co/2DINsrC
Do you want to help improve disaster communications?
Do you want to use your AREDN network as a foundation for solutions to improve disaster relief efforts?
Do you develop computer applications and want to help improve disaster communications? AREDN asks you to make a difference with your code.
This year's Call for Code program decided to add an emphasis on healthcare needs in the lead up to and aftermath of natural disasters. The program's Chief Technology Officer (CTO) Daniel Krook writes "Specifically, we’re calling on developers to create solutions that address the following aspects of healthcare:
We based our healthcare...
Read MoreTheme by Danetsoft and Danang Probo Sayekti inspired by Maksimer