Question for you: If a mountain top site upgrades to an AC unit, can a mix of 802.11N and 802.11AC units run at their native speeds or would all stations be restricted to run at 802.11N?
Showing posts with label AREDN Firmware. Show all posts
Showing posts with label AREDN Firmware. Show all posts
AREDN Linking 802.11N and 802.11AC units question
AREDN Linking 802.11N and 802.11AC units question
Question for you: If a mountain top site upgrades to an AC unit, can a mix of 802.11N and 802.11AC units run at their native speeds or would all stations be restricted to run at 802.11N?
Question for you: If a mountain top site upgrades to an AC unit, can a mix of 802.11N and 802.11AC units run at their native speeds or would all stations be restricted to run at 802.11N?
AREDN 802.11ac replacements for existing gear
802.11ac replacements for existing gear
Attached is a doc that shows some 802.11ac devices that are appropriate for new installs, or upgrades of existing equipment. While the software for them is still in the nightly builds, the software is stable and they'll be included in the next production release, which should be soon.
All 802.11ac devices:
Attached is a doc that shows some 802.11ac devices that are appropriate for new installs, or upgrades of existing equipment. While the software for them is still in the nightly builds, the software is stable and they'll be included in the next production release, which should be soon.
All 802.11ac devices:
- Have Gigabit Ethernet ports, two in some cases, and five for the Mikrotik hAP ac2 & ac3
- Have faster CPUs
- Have more RAM
- Most have more flash memory
- Appear to have more sensitive receivers
- Report true noise level
booth at SCALE this year 2023
There's a photo attached of the team manning the AREDN booth at SCALE this year.
Left to right:
Front: KE6BXT, KM6SLF.
Rear: KJ6DZB, KN6PLV, N6RFI. W6BI. Missing: KG6WXC
And this year SCALE attendees voted the AREDN booth as "Best Presentation"
Left to right:
Front: KE6BXT, KM6SLF.
Rear: KJ6DZB, KN6PLV, N6RFI. W6BI. Missing: KG6WXC
And this year SCALE attendees voted the AREDN booth as "Best Presentation"
AllStar over AREDN
Is it possible or has anyone established an AllStar link over AREDN?
I have two projects in mind actually.
We are line of sight, about 10 miles apart. I have a dual WAN router at my place and want to set it up so if my ISP goes down the network switches to the RF link to my dad’s place and service to the users continues for the Pi’s at my QTH.
I have two projects in mind actually.
I have distributed the pi’s that form the network so there is some geographic redundancy between my place and my dad’s (also a ham). We have backup power which is good. He is also using a different ISP so we have vendor diversity.
We are line of sight, about 10 miles apart. I have a dual WAN router at my place and want to set it up so if my ISP goes down the network switches to the RF link to my dad’s place and service to the users continues for the Pi’s at my QTH.
Overview for the Modern, Digital HAM Radio Operator
Overview for the Modern, Digital HAM Radio Operator
youtu.be/oYKoixN0r54
AREDN Firmware Update 3.22.8.0 🚨 NEW
The AREDN dev team has shifted into high gear (this is the third release of 2022)! This production release adds the many fixes and enhancements made since 3.22.6.0.
by W6BI Orville Beach
Fixes
Dealt with LAN on AR300M always having the same MAC address.
Fixed default DHCP limits in NAT mode if fields are blank.
Fixed a "do not propagate" issue when reserving DHCP names.
Fixed tactical names.
Fully validate node and tactical names; give better messages when invalid.
Prevent < and > from being used in service names.
Correct map update claiming success when it actually fails.
Added device definition for Ubiquiti PBE M5 300-ISO.
Some Ubiquiti Powerbeams: keep 100MB as the only port speed, but let the port auto-negotiate with the switch to fix throughput issues.
Fixed display of unknown radio models.
AREDN Release Notes v3.20.3.0 – 27 March 2020
AREDN Release Notes v3.20.3.0 – 27 March 2020
The AREDN team is pleased to announce the general availability of the latest stable release of AREDN firmware. We now fully support 70+ devices from four manufacturers. This diversity of supported equipment enables hams to choose the right gear for a given situation and budget.
AREDN firmware is now based on the most recent stable version of OpenWRT19.07.2 which was released in March 2020. This improvement is significant in that it enables AREDN firmware to benefit from the many bug fixes, security improvements and feature enhancements provided by OpenWRT developers from around the world.
The AREDN team is pleased to announce the general availability of the latest stable release of AREDN firmware. We now fully support 70+ devices from four manufacturers. This diversity of supported equipment enables hams to choose the right gear for a given situation and budget.
AREDN firmware is now based on the most recent stable version of OpenWRT19.07.2 which was released in March 2020. This improvement is significant in that it enables AREDN firmware to benefit from the many bug fixes, security improvements and feature enhancements provided by OpenWRT developers from around the world.
AREDN v3.18.9.0 Release Discussion
AREDN v3.18.9.0 Release Discussion
This isn't the first time I have had AREDN developers and information on this show, and I promise it won't be the last either. MESH networking is a pinnacle definition of "What is new in Amateur Radio" and I thoroughly enjoy talking about it and experimenting with it.
In this episode, I get to speak with Darryl and Joe from the developer team about the new 318 firmware - what changes were made and what new hardware has been added to the supported list of devices.
This isn't the first time I have had AREDN developers and information on this show, and I promise it won't be the last either. MESH networking is a pinnacle definition of "What is new in Amateur Radio" and I thoroughly enjoy talking about it and experimenting with it.
In this episode, I get to speak with Darryl and Joe from the developer team about the new 318 firmware - what changes were made and what new hardware has been added to the supported list of devices.
Mobile AREDN Mesh Networking
Mobile AREDN Mesh Networking
It’s been a while since I’ve written anything – lots going on, both radio and non-radio related, and I don’t have the time to write as much as I’d like to. So I thought I’d take a few minutes to talk more about Mesh Networking, the AREDN, and operating mobile.
It’s been a while since I’ve written anything – lots going on, both radio and non-radio related, and I don’t have the time to write as much as I’d like to. So I thought I’d take a few minutes to talk more about Mesh Networking, the AREDN, and operating mobile.
BBHN vs AREDN Firmware Discussion
Mar 25, 2015 - If you are just starting out with mesh experimenting and go looking for firmware, the first thing you will discover is that there are now two different ham mesh projects. One is named BBHN the other AREDN. Here is what I have been able to determine by poking around. I have sent this same info by email to several users so it may be old news to some, but in order to get everyone up to speed here it goes again..
In regards BBHN vs AREDN, there is a bit of controversy right now. At the moment they are exactly the same firmware with the exception of the SSID that is set. A short summary of the situation is that there are two main groups working on the Ham mesh project. One is in Texas around Austin, the other in CA in the San Diego area. The Austin group did the original mesh modifications to OpenWRT, the base OS, using the WRT54 platform. Many continue to use the Linksys routers today. That initial project was called HSMM. The San Diego team developed the later versions of the firmware that were renamed BBHN, and started supporting the more capable Ubiquiti radios. Most recently the SD guys wanted to drop support for WRT altogether. They site the vast superiority of the Ubiquiti gear and the fact that the firmware features they want to add in the future won't fit in the WRT's limited memory. This lack of WRT support was a strong point of disagreement between the two groups and a "divorce" resulted. This happened in the last month or so. The average users were basically in the dark during the "breakup";
In regards BBHN vs AREDN, there is a bit of controversy right now. At the moment they are exactly the same firmware with the exception of the SSID that is set. A short summary of the situation is that there are two main groups working on the Ham mesh project. One is in Texas around Austin, the other in CA in the San Diego area. The Austin group did the original mesh modifications to OpenWRT, the base OS, using the WRT54 platform. Many continue to use the Linksys routers today. That initial project was called HSMM. The San Diego team developed the later versions of the firmware that were renamed BBHN, and started supporting the more capable Ubiquiti radios. Most recently the SD guys wanted to drop support for WRT altogether. They site the vast superiority of the Ubiquiti gear and the fact that the firmware features they want to add in the future won't fit in the WRT's limited memory. This lack of WRT support was a strong point of disagreement between the two groups and a "divorce" resulted. This happened in the last month or so. The average users were basically in the dark during the "breakup";
Subscribe to:
Comments (Atom)