开云体育

Here are some metrics on our AREDN network (real stuff - not an April Fool's joke :-) ) 2856 nodes seen on supernode network. Of them, 63 are supernodes Longest uptime - 810 days: VE7URC-oldPO-VE7BCE Oldest hardware: M0XZL-L7, M0XZL-L1: WRT54Gs (running BroadbandHamnet v3.0. :-D Oldest AREDN software: - GM0RAY-2: running 3.18.9.0 on an AirRouter HP. Nodes running current nightly builds (Babel-enabled nodes): 631 That's (631/2856=) 22.1% - we're getting there. Nodes running the tiny build (meaning they can't run the Babel protocol): 117 That's (117/2856=) 4.1% Those are the models that will drop off the network at some undefined point in the future: AirGrid M2 XM AirGrid M5 XM AirGrid M5 XW AirRouter AirRouter HP Bullet M2Ti Bullet M5 Bullet M5Ti Bullet M2 NanoBeam M2 NanoBridge 2 NanoBridge 5 NanoStation Loco M2 NanoStation Loco M5 NanoStation Loco M9 NanoStation M2 XM NanoStation M3 XM NanoStation M5 XM Note that while these devices are old and slow, the XW versions of them have enough RAM to not have to run the tiny build. All the major changes planned for the next production release are in the nightly builds. We hope to release that production build in a month or so but it would be helpful if more folks wrung out the nightly build. Although it seems stable with no known issues, we'd like to get more eyes on it. While the AREDN team has a few metrics to compare the Babel routing protocol performance to the OLSR performance, anecdotally we've heard that if your network has a significant percentage of Babel-enabled nodes, the performance and stability is noticeably improved. What's your experience been? 73 Orv W6BI AREDN Project Manager

Some AREDN-related tidbit. The AREDN World Map is updated four times per day: 0200, 0800, 1400, and 2000 UTC. If you're going to run a supernode, make sure it's wired to the network; it needs to have a solid connection 24x7. AREDN is now recommending the OpenWRT One for use as a supernode, superseding the ac2. On Amazon, it's sold as the "MiiElAOD Banana Pi OpenWrtOne Router", currently for $105, or the "WayPonDEV Banana Pi WiFi 6 OpenWrt One Router Board " for $119. . While that's more than an ac2 would cost at $78, the OpenWrt One is substantially more powerful, with more memory. As of this writing, only 4.3 percent of the nodes on the supernode network are running a tiny build and won't be able to run a Babel-enabled software. Their breakdown: Nanostation XM - 43 Nanobridge XM - 9 Bullet- XM - 44 Airrouter- 28 (XW versions have more memory and are OK) Note: Bullets do come in an XW version, but they're not MIMO. They're on the Sunset list for that reason. Total - 124 (out of close to 3,000 nodes) When the OLSR routing protocol is dropped from AREDN sometime in the future, legacy tunnels will stop working, as they can't support the Babel protocol. Users have been advised to migrate from legacy tunnels to Wireguard tunnels for some time. A recent change to the code enables legacy tunnels to be broken out from Wireguard tunnels in their JSON file. Of those nodes that have picked up this change, they report 17.5% legacy tunnels, 82.5% Wireguard tunnels. Not too shabby! 73 Orv W6BI

From Tim KN6PLV, the AREDN lead developer: I want to encourage people to experiment with the current AREDN nightly build. It would be good to have more eyes on the Babel changes (better route filtering) in more diverse spots in the network. Thanks. Orv W6BI AREDN Project Manager

To all, I just got a phone call from one of my buddies in TX… It appears I was clear as mud in my last email… 99% of those joining are only joining the Root group for each Division and didn’t see the list of Sections listed for each Division… It was clear in my mind... Below is the EXPANDED list showing the 15 Divisions and the 100+ Section subgroups… Another thing pointed out to me… When you join a Section subgroup you are automatically added to the parent Division group… Example; If you join the Georgia Section you will automatically be in the Southeastern Division… Links to the 15 Division email groups: https://arrl-atlantic-div.groups.io/g/main Delaware Section Eastern Pennsylvania Section Maryland-DC Section Northern New York Section Southern New Jersey Section Western New York Section Western Pennsylvania Section https://arrl-central-div.groups.io/g/main Illinois Section Indiana Section Wisconsin Section https://arrl-dakota-div.groups.io/g/main MN - Minnesota Section ND - North Dakota Section SD - South Dakota Section https://arrl-delta-div.groups.io/g/main Arkansas Section Louisiana Section Mississippi Section Tennessee Section https://arrl-great-lakes-div.groups.io/g/main Kentucky Section Michigan Section Ohio Section https://arrl-hudson-div.groups.io/g/main Eastern New York Section New York City - Long Island Section Northern New Jersey Section https://arrl-midwest-div.groups.io/g/main Iowa Section Kansas Section Missouri Section Nebraska Section https://arrl-new-england-div.groups.io/g/main Eastern Massachusetts Section Maine Section New Hampshire Section Rhode Island Section Vermont Section Western Massachusetts Section https://arrl-northwestern-div.groups.io/g/main Alaska Section Eastern Washington Section Idaho Section Montana Section Oregon Section Western Washington Section https://arrl-pacific-div.groups.io/g/main East Bay Section Nevada Section Pacific Section (Hawaiian Islands) Sacramento Valley Section San Francisco Section San Joaquin Valley Section Santa Clara Valley Section https://arrl-roanoke-div.groups.io/g/main North Carolina Section South Carolina Section Virginia Section West Virginia Section https://arrl-rocky-mountain-div.groups.io/g/main Colorado Section New Mexico Section Utah Section Wyoming Section https://arrl-southeastern-div.groups.io/g/main Alabama Section Georgia Section Northern Florida Section Puerto Rico Section Southern Florida Section Virgin Islands Section West Central Florida Section https://arrl-southwestern-div.groups.io/g/main Arizona Section Los Angeles Section Orange Section San Diego Section Santa Barbara Section https://arrl-west-gulf-div.groups.io/g/main North Texas Section Oklahoma Section South Texas Section West Texas Section Feel free to join the Division(s) and Section(s) you want. For Division Directors and Section Managers, the volunteer Admins will confirm your email address and upgrade you to Moderator status so you can post announcements, and newsletters and make other changes. 73 Dallas N4DDM

To all, The ARRL Georgia Section email service is back… This system has been offline since the ARRL was hacked back in May… Recently a small team of volunteers created 15 groups on 开云体育 for the 15 Division Directors and Section Managers. List of Features: A group for each of the 15 Divisions with subgroups for the Sections in that Division All are configured for Top-Down, 1-way announcements and newsletters At some future date, other Leadership members such as.: Section Emergency Coordinators Affiliated Club Coordinators Public Information Coordinators These could be one-time messages or new subgroups 开云体育 gives us the flexibility to do this The ARRL system only allowed Plain Text messages. 开云体育 gives you a choice of Rich Text, Plain Text, and other delivery options Groups allow newsletters/announcements with graphics and hypertext links Subscribers may subscribe to as many Divisions and Sections as they want ARRL members were only allowed one Division and one Section Non-Hams and non-ARRL members can subscribe Calendars for Events at the Division and Section levels are available Each Division group shares 1GB of storage for Files and Photos Old attachments self-delete to make way for new ones when space is limited 开云体育 supports #Hashtags and Special Notices Many of us have been using 开云体育 in one way or another for decades One thing we learned from the IT attack is that having a 2nd independent communications system is a good idea Tim E18IC has an excellent ARRL Division Map showing the Divisions and Sections to help our ham community choose which groups to join. Check out his other maps and buy him a cup of coffee. Links to the 15 Division email groups: https://arrl-atlantic-div.groups.io/g/main https://arrl-central-div.groups.io/g/main https://arrl-dakota-div.groups.io/g/main https://arrl-delta-div.groups.io/g/main https://arrl-great-lakes-div.groups.io/g/main https://arrl-hudson-div.groups.io/g/main https://arrl-midwest-div.groups.io/g/main https://arrl-new-england-div.groups.io/g/main https://arrl-northwestern-div.groups.io/g/main https://arrl-pacific-div.groups.io/g/main https://arrl-roanoke-div.groups.io/g/main https://arrl-rocky-mountain-div.groups.io/g/main https://arrl-southeastern-div.groups.io/g/main (This is the one for us in Georgia) https://arrl-southwestern-div.groups.io/g/main https://arrl-west-gulf-div.groups.io/g/main Feel free to join the Division(s) and Section(s) you want. For Division Directors and Section Managers, the volunteer Admins will confirm your email address and upgrade you to Moderator status so you can post announcements, and newsletters and make other changes. 73 Dallas N4DDM Hank's email follows... ----- Forwarded Message ----- From: ARRL Members Only Web site <memberlist@...> To: "mylastname@..." <mylastname@...> Sent: Monday, March 17, 2025 at 11:04:10 AM EDT Subject: March/April Georgia On My Mind Newletter Hey folks... The ARRL has the Georgia Section email service back up and working!!! See the link below for the newsletter, but first I want to thank all of the ARES members, Skywarn Coordinators, weather spotters, repeater owners, ham volunteers at PTC, and anyone else who helped with the storm coverage over the past weekend - Thank You! I received kudos from several local agencies for the work involved in helping the NWS, GEMA, and you neighbors be safe and stay informed. Newsletter link: https://drive.google.com/file/d/1MqfDEyu0ZyYQl54aAzl79ngoIRz-oqGK/view?usp=drive_link Until nest time! 73 Hank, K4HYJ EC Whitfield Co ADEC NW GA District SM Ga -------------------------------------------------------------------- ARRL Georgia Section Section Manager: Henry O Blackwood Jr, K4HYJ k4hyj@... -------------------------------------------------------------------- About this Email: You are receiving this email because you are subscribed to receive ARRL Division and Section News. To manage your ARRL e-newsletters and notifications, please visit www.arrl.org/opt-in-out. You must be logged in to the ARRL website to edit your email subscriptions. Copyright ? 2025 Amer

From a FaceBook post via Repeaterbook: It is with a heavy heart that we share the passing of one of our most dedicated and beloved Admins, Chuck Adams, KV4VT. Chuck was officially the Admin for Georgia but played a vital role far beyond his home state. He assisted with repeater coordination across the country, recruited new volunteers, and mentored many of us along the way. More than anything, Chuck was a passionate believer in the RepeaterBook project, championing it at every opportunity. He was instrumental in expanding our presence within the amateur radio community. When Chuck asked if he could represent RepeaterBook at a booth in Huntsville, it marked a significant milestone—it was our first-ever booth, and he ran it entirely on his own. He later reported back with excitement about the overwhelmingly positive reception and the deep appreciation for RepeaterBook among operators. Chuck’s enthusiasm was infectious. He convinced me to attend HamCation in Orlando in 2024, where we hosted another booth. Our app developer, Nicolas (M1HOG) from England, joined us. As always, Chuck was right—it was an incredible experience, filled with camaraderie and shared passion for the hobby. The photo here is from that event, with Chuck at the center, proudly wearing his blue sports coat. Later that year, I also attended Dayton. This year, however, Chuck was unable to make it to HamCation. Yesterday, I received the heartbreaking news that he had passed away. Chuck was an extraordinary man—kind, selfless, and always willing to lend a hand. The saying, “He’d give you the shirt off his back,” was more than just words in his case—it was who he was. His absence leaves a void in our community, but his legacy and the impact he had on all of us will live on. Rest in peace, Chuck. You will be deeply missed. 73 Dallas N4DDM 73 Dallas N4DDM Whatever you do, don’t fall victim to “paralysis by analysis.” Go ahead and buy/build one and start tinkering with it. This is a learn-by-doing hobby. No politician or scholar assured your freedoms. A Soldier, Sailor, Marine, Airman, or Guardian did!

When AREDN spun off from Broadband Hamnet around 2013 they inherited OLSR, the Optimized Link State Routing Protocol. Version 1 was developed in 2003. It was pretty quickly deprecated due to known deficiencies, but AREDN was stuck with it. Several years ago in an effort to help users optimize their links, LQM, the Link Quality Manager, was developed. It allowed nodes to ignore really weak stations, to set minimums on SNR and maximums on link distance. All these would help to maximize the use of precious bandwidth by trying to minimize retries. With the advent of the Babel routing protocol, developed in 2021 and adapted by AREDN recently, there's no need for LQM - the Link Quality Manager has become the Link Quality Monitor. You'll see those changes in nightly build 20250306. Additionally, the Wireless Watchdog LQM will be removed; it's no longer needed. Orv W6BI AREDN Project Manager

We think today's nightly build has addressed the memory issues we’ve been seeing. While there were certainly a few memory leaks fixed along the way, and we now also support zram swap, the final bug looks to have been a change in the vm.min_free_kbytes setting. This was being set to 16M per core, so it could easily reserve half of available memory for the system “just in case” use (making it unavailable for use by applications). We’ve dropped this back down to 1M per core, and have seen many hours of stability in places we were lucky to get an hour from. This nightly build is pretty much a "must have" if you're running supernode tunnels on an ac2, and "highly-recommended" if you're running tunnels on a hAP ac Lite Again, test with caution, but we're comfortable that the memory issues are behind us. AREDN Dev Team

The implementation of Babel and the Point to Point protocols has revealed some memory management issues that eventually degrade performance. Some issues were found in modules and libraries that AREDN borrows from OpenWrt, and were addressed. However, we're still seeing a few memory issues. A note just from Tim KN6PLV, the lead dev: "I’m just working through various reports of what causes the oom-killer to trigger when it's not expected. At this point it's not running out of memory, as I can see it being triggered with 44M free, but there are various reasons (including kernel bugs) people are noting might be an issue. So just need to work out which is our problem." For those not familiar with the term, "OOM" refers to an out-of-memory condition in an operating system. OSes try desperately to avoid that condition through the use of virtual memory and swap, but it does occur. Linux tries very hard to keep running through the use of the oom-killer, but its application still tends to be a bit "indiscriminate"... In AREDN's case it appears to be mostly directed at OLSR. So while you can test the nightly builds, it's not recommended that you put them into remote nodes just yet. I'll send an all-clear note when we believe the memory issues have been fully addressed. 73 Orv W6BI AREDN Project Manager

This is derived from the AREDN World Map (https://worldmap.arednmesh.org/#1.5/35/-14 ). If your local network isn't connected to that network your nodes won't be included. Number of AREDN nodes: 2897 Number of AREDN supernodes: 59 Number of nodes on sunsetted hardware on the network: 145 (5.0% - down from 5.8% last month) Longest uptime: VE7URC-oldPO-VE7BCE - 779 days Oldest hardware still on the network: KI4QWT-PSM2-150-HSV - a Ubiquiti PicoStation M2 Nodes that are 802.11ac: 261 (9%) Oldest software version: GM0RAY-2, running 3.18.9.0 Runner-ups, running 3.19.3.0: K7DMK-N13 K7ZAE-B-NE K8IO-QTH-M2 ka2vlp-m900-1 KG7AHP-M9-01 KG7BZ-M5-NanoB-W7VA VE6CV-hAP-YQL VE6TL-ARHP-AP VE7URC-OldPO-North W4NMH-U1 W6BB-Evans-Nano5g-SW W7VA-M5-NanoB-Lebanon WB9KMO-R2-SW120D There are a few nodes running nightly builds that predate the current numbering scheme that are likely quite old: node firmware_version AC0EC-MCC-HAP-Router 1611-9214a74 KE0AVT-Aerial 1158-340cd76 KG7HMZ-NSM2-East-MFR 1709-e377086 KJ6IUV-RM5-120SE 1253-276d141 KM6ASI-San-Rafael 1874-eb631e4 N0MRZ-Mobile 1222-77c88f2 N0ZL-IDEC-hAP-QTH 1819-283938c Nodes running the current production release (3.25.2.0) or a newer nightly build: 1251 (43.2%) Nodes running the previous production release (3.24.10.0) or a newer nightly build: 759 (26.2%) So almost 70% of the network is running software that's 5 months or less old. Not too shabby! There have been a couple of exciting additions to the recent nightly builds: The Babel routing protocol has been added, alongside OLSR. It's loop-free, and only sends network changes when they occur, rather than constantly like OLSR does. If both ends of a link find themselves "Babel-enabled" they will use Babel preferentially. PtP (Point to Point) and PtMP (Point to MultiPoint) protocols have been added. Because they operate in infrastructure mode rather than AREDN's traditional ad hoc mode, they tend to be more efficient. We've also seen that links in these modes that have 802.11ac hardware on each end have significantly better throughput than legacy 802.11n hardware does. HOWEVER - the implementation of these protocols have revealed some memory management issues that eventually degrade performance. Some issues were found in modules and libraries that AREDN borrows from OpenWrt, and were addressed. However, we're still seeing a few memory issues [tl;dr: OLSR is being a butt-head]. So while you can test the nightly builds, it's not recommended that you put them into production networks just yet. 73 Orv W6BI AREDN Project Manager

To all, What type of forums do y'all want? I need suggestions, I need volunteers... Tell me about forums/club presentations you heard about or attended... Atlanta Hamfest 2025 - June 7th - Jim Miller Park https://www.atlantaradioclub.org/atlanta-hamfestival-forums.html Stone Mountain HamFest 2025 - November 1st - Gwinnett Co Fairgrounds https://stonemountainhamfest.com/index.php/forums/ Feel free to reply 1-on-1 or copy whoever gave the talk to me at: dallas.n4ddm@... 73 Dallas N4DDM 512-560-9074 Whatever you do, don’t fall victim to “paralysis by analysis.” Go ahead and buy/build one and start tinkering with it. This is a learn-by-doing hobby. No politician or scholar assured your freedoms. A Soldier, Sailor, Marine, Airman, or Guardian did!

After a couple of rounds of nightly builds stomping out bugs, we have a working PtP ? Mesh Station on a live network link. Here are the basic steps: Bring both ends to latest nightly builds. Get far end / Station MAC address (click on the Radio section - the MAC address will be shown at the top of the dialog) Copy the MAC address. Configure far end node as a Mesh Station (requires Commit & Reboot) Switch the near end node to PtP mode - a field will appear to paste the far end MAC address in. Commit & Reboot. The link will come up PtP ? Mesh station Notes: The nodes can take almost 4 minutes to come up; be patient. A quick and dirty before & after test of throughput (802.11ac devices on both ends): Before: Ad Hoc mode: 10-12 Mbit/sec After: Infrastructure mode: 20-21 Mbit/sec; a nice bump in throughput (obviously YMMV!) 802.11n links show little or no improvement in throughput (again YMMV). This is Experimental - if the user community finds it's not all the useful, it may be removed. Feedback desired!

All, The ARISS contact at Woodward Mill Elementary School is scheduled for Thursday (20th) 11:37:28 EST, (16:37:28 UTC). If you want to watch the entire program, tune into the live stream an hour earlier. YouTube Link; https://www.youtube.com/live/NfxlSEUOg6A For those that would like to listen to the ISS directly tune in to: 145.800MHz. You will only hear the astronaut side of the conversation. 73, Over Ralph Pickwick KJ4CNC Education Chairman Reposted by: 73 Dallas N4DDM

Following on the heels of the inclusion of the Babel routing protocol to the AREDN software is another significant enhancement: nightly build 20250219 adds PtP (Point to Point) and PtMP (Point to MultiPoint) configurations. These protocols can be found in the Radio section of the AREDN UI: Here's a brief explanation of each of them: Mesh PtMP: This makes a node act like your common access point, where Mesh Station nodes can connect to it, but not to each other, and the Mesh PtMP can only connect to Station nodes. Mesh PtP: Same as above except only a single Station is permitted to connect, specified by a MAC address. Mesh Station: Can connect to a Mesh PtMP or, if it’s the authorized node, a Mesh PtP. It cannot connect to anything else. The new modes also require a new SSID. This changed SSID is a necessary by-product of how these modes are implemented. Our current Mesh uses the WiFi Ad-Hoc radio mode, while these new modes use the WiFi Infrastructure (sometimes called Manager) radio mode. Infrastructure Stations will connect by matching the appropriate SSID, without regard for any channel setting. Therefore, to make sure Stations connect to their correct end-point, we encode the channel in these new SSIDs. For example, if you have a Mesh PtMP node on channel 175 at 10 MHz, the SSID would be AREDN-175-10-v3. Consider this feature EXPERIMENTAL. We are releasing it for feedback from the community. We know that Infrastructure radio mode is better supported and we suspect it provides better compatibility between vendors compared to AdHoc mode, and supports higher bandwidths. We’d like to get feedback from the community to see if this is true, if this is useful, and if it’s worth the support costs of including this in future releases.

The AREDN team is introducing a new networking technology into the nightly builds with the ultimate long term goal of replacing OLSR. OLSR has many faults which AREDN has lived with for a long time. For the last couple of years we’ve been looking at alternatives and making incremental steps in the codebase to allow us to introduce something new. We can finally do that by adding Babel (https://www.irif.fr/~jch/software/babel/) to AREDN. Babel has a number of qualities which make it good for AREDN. First, it’s a loop free protocol so, regardless of how the network is changing, routing loops will never form in the network. Second, it’s primarily a reactive protocol which sends changes to neighbors when needed rather than broadcasting its state continually. Third, the protocol understands the difference between wired, wireless, and tunneled links – the three link types AREDN utilizes. Fourth, it’s a layer-3 routing protocol, which integrates easily with how AREDN already operates. Fifth, it’s highly configurable which will allow an optimal setup for our use case. Finally, it’s simple. We considered a number of options, and another contender was B.A.T.M.A.N. Advanced. Unfortunately this protocol is not a good fit for AREDN as it primarily focuses on level-2 wireless networking. AREDN needs a protocol which can do more. We evaluated how we could use BATMAN and it wasn’t simple, efficient or pretty. If you’re interested in more comparisons between Babel and other options there are many good presentations on YouTube. This is a great primer on Babel itself: https://www.youtube.com/watch?v=1zMDLVln3XM Babel will roll out into the nightly builds alongside OLSR and the two will operate in parallel. If there is a Babel-only path between two nodes in the network, then Babel routes will be used to send traffic. If not, then OLSR routes will be used. This will let us deploy Babel and examine its performance in our networks without disturbing nodes which are not running Babel. Important: Be aware that older radios with limited memory – the ones using the tiny firmware images – will not be able to support both protocols and should be eventually replaced. Evaluating success will depend on a few things, and the more feedback from the community the better. Our goals are to provide a more stable network, better routing decisions, and lower network overhead. Assuming success, the time scale to replace OLSR will be measured in years. Once OLSR is gone, any node not running Babel will disconnect, and we don’t want to leave our users behind so we are giving this as much time as needed for the transition to the newer protocol. The AREDN development team

All, The ARISS contact at Woodward Mill ES is scheduled for Thursday (20th) 11:37:28 EST, (16:37:28 UTC). If you would like to watch the entire program, tune into the live stream an hour earlier. For livestream go to YouTube.com, then search ARISS Woodward Mill ES. For those that would like to listen to the ISS directly tune in to: 145.800MHz. You will only hear the astronaut side of the conversation. 73, Over Ralph Pickwick KJ4CNC Education Chairman

AREDN Product Release 3.25.2.0 is now available for download. Here's an overview of the fixes and enhancements in this release. All of these changes have been thoroughly tested throughly via the nightly builds and our intrepid band of testers! Features New Mobile UI Backup and Restore node configurations Responsive design for desktop UI on smaller screens Improved logged-out experience to provide more information Improved WiFi Signal tool which shows SNR at both ends of link Support for ARDC’s 44-Net Upgraded to the latest OpenWRT release: 24.10 Notes By default LAN devices are no longer permitted to access the Internet over the mesh. This can be re-enabled if required. The old UI is no longer available. We recommend the High Contrast theme when using the mobile UI outside. The new WiFi Signal tool requires both ends of a link be running the latest firmware. Enhancements Added more USB controller modules #1878 Added usbutils loadable package #1875 Improved firewalling of LAN #1862 Made further improvements to LAN to WAN firewalling. #1863 Enabled 44NET LAN configurations #1548 Enabled kmod-eeprom-at24 package #1529 Made watchdog improvements #1322 Now report IP Address at the end of command line setup. #1861 Now allow local NTP server to run as a service for LAN devices #1865 Now allow ping and traceroute to auto select the best interface #1856 Animated the commit message like the scan message #1839 Added rpcapd loadable package to aid remote node monitoring #1838 Added disconnect reporting #1831 Now throttle dnsmasq restarts when names change #1826 Improved messaging in various parts of the network setup #1817 Now attempt to guess PC hardware and better support unknown hardware (for VMs). #1816 Include main IP address in HNA4 records #1814 Dnsmasq performance improvements. #1813 QEMU User Agent now available as a module for x86 build #1798 Improved mesh device and service counts #1796 Moved the LAN DHCP enable/disable option into the LAN DHCP panel #1788 Improved tunnel "email" messaging #1773 Support forcing DHCP options without a specific tag #1769 Open a new tab for help and website menu links #1760 Improvements to the wifi watchdog #1757 Added a basic syslog tool #1744 Supernodes now support 44net by default #1753 Now provide 44net route override #1703 Added rapid-commit (dhcp) option #1733 Added command line tool to generate support data #1695 Added command line backup util #1729 Sped up commits #1721 Added DHCP option validation #1718 Now support DHCP options without values #1735 Gave high contrast theme wider dialogs (now we support that) #1716 Now support non-admin neighbor info in mobile view. #1714 Improved help for mobile wifi signal tool. #1693 Improved display of blocked neighbors #1709 Provide proxy and redirect for problematic services #1699 Now allow scanning of non-mesh and multiple wifi devices #1578 Made tunnel server name optional if you have no server tunnels #1688 Now support pasting lat,lon coordinates into either lat or lon map field #1687 Now support Y.X style radio heights #1673 Now filter the LAN name from node hosts #1669 Added pseudo services for Local Devices #1665 Now allow packages to be removed on low memory nodes. #1684 Improved detection and display of services and devices #1683 Improved which local devices and service we show when logged out or logged in. #1682 Provide UI for the wifi watchdog system. #1655 Improved tunnel messaging #1648 Added topology info to sysinfo.json #1637 Improved startup of LQM so we get some information early #1632 Support wider channels (experimental) #1631 #1635 Split the Wifi Signal gauge to show the local and remote signal information #1602 #1628 Improved detection of disconnected nodes #1617 Periodically sync time if continuous NTPD is unsynchronized #1611 Now include cookies when testing services. #1600 Improved antenna settings messaging #1605 Added VHT support (experimental) #1630 Decimate the neighbor graph data so we can show more history #1598 Added capability to backup and restore node configurations #1597 Added secondary NTP server option #1583

GARS TechFest - This Saturday, February 1st 2025 Final Reminder for TechFest 2025 Exhibitors/Clubs - Set up at 7:00 AM - 8:30 AM Public - 8:30 AM - 3:15 PM Ham Exams - 9:00 AM - 11:00 AM Lunch - 11:30 AM - 1:30 PM Forums - 9:00 AM - 3:00 PM Final Prize Drawings - 3:15 PM Clean Up - Right after the Final Prize Don’t miss the: Balloon Launch - 9:45 AM Chili Cook-off - Info here FREE Hot dog Lunch with all the fixings 10 Forums - Listed here 34 Clubs/Exhibitors - Listed here Raffel Prizes - Listed here Door Prizes - Too many to list… Gwinnett Co Fairgrounds - Davis Rd Entrance Display Tables are 2.5x8 feet; Plan on bringing; display flyers, tablecloth (club/school colors of course) banners, flags, photos, and info about your club showcasing past and future events. If your table needs power bring a 25’ extension cord and power strip. What is TechFest? Visit our Home Page at www.techfest.info and find out. Our Big Event will be Jack McElroy KM4ZIA and his High Altitude Balloon Launch with a WSPR transmitter onboard so we can track it on APRS.fi as it flies around the globe. In the FREE column: Free Parking Free Admission Free Forums - See the list Free Tables for clubs/groups to showcase what they do - See the invited list Make sure your club/group has a table - Fill out this online form Free Ticket for Hourly Door Prizes Chili Cook-off - More info and sign up here Free Hotdog/Chili dog lunch with all the fixings Free Coffee/Water/Sodas Tour of the GA AUXCOMM Trailer Tour of the Gwinnett ARES Trailer Dozens of club/group tables - Make sure yours is there In the Not-Free column: Ham Exams - $14 Cash, more info on our home page Raffle Prizes - $5 each or 5 for $20 - list of items to be posted soon Buy your Raffle Prize Tickets Online - Info here Please forward this email to any clubs/groups I missed. I hope to see you at TechFest. 73 Dallas N4DDM

Astute users have noticed my typo in this email :-/ Corrected text below. 73 Orv W6BI -------- Forwarded Message -------- Subject: AREDN Heads-up; behavior change coming Date: Tue, 28 Jan 2025 20:38:35 -0800 From: Orv Beach <orv.beach@...> This may only affect a few users, but the dev team thought we should put the word out so no one was surprised. The nightly build that will be released as 20250129 changes a firewall behavior. As it is now by default, if your node (usually a hap of some sort) didn't have a WAN connection, it would go out over the mesh to find an Internet link. It was difficult to make sure this wasn’t happening and not very obvious how to prevent it. The change implemented in tomorrow's build is the addition of a new switch which will determine if LAN devices of your node can reach the Internet over the AREDN network. And it will be defaulted to off which is a change from current behavior. 73 Orv W6BI AREDN Project Manager