# Check out the ASL3 Announcement **URL:** \ **Category:** AllStarLink\ **Tags:** asl3\ **Created:** [June 29, 2024, 4:30pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241 "2024-06-29T16:30:04Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [June 29, 2024, 4:30pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/1 "2024-06-29T16:30:04Z")
Not sure everyone here views the Announcements Category so… Here’s a link to the ASL3 announcement. > [@ASL3 Beta Announcement](https://community.allstarlink.org/t/asl3-beta-announcement/21240): > > AllStarLink is proud to announce ASL3, the next generation of AllStar repeater and hotspot software. ASL3 is built to run on Asterisk 20, the latest operating systems, and modern hardware. Asterisk 20 brings over 15 years of bug fixes, security improvements, and enhancements. Naturally, ASL3 benefits significantly from running on Asterisk 20. But we didn’t stop there. ASL3 is easier to install and use thanks to a new fully functional Raspberry Pi image. To get started, check out the Raspberry P… This has been a huge undertaking for the ASL Team. They have not only brought AllStar up to current Asterisk release, current Debian OS, but also put a very nice polish in the Raspberry Pi version. It looks like this. ![Screenshot 2024-06-29 at 9.20.02 AM](https://community.allstarlink.org/uploads/default/original/2X/d/d842fa968477e5ad81875e7f5a8b22e5081133e7.jpeg) For folks that run intel systems, ASL installs with apt update and apt upgrade. It doesn’t have all the bells and whistles the Pi does but many AllStar builders don’t need the frill or add their own. And I have to add that our work is open for all to see and use according to the spirt and letter of open source. So enjoy. Let us know what you think. ---
**Author:** ![NR9V](https://community.allstarlink.org/user_avatar/community.allstarlink.org/nr9v/32/2195_2.png) [@NR9V](https://community.allstarlink.org/u/NR9V)\ **Post date:** [June 29, 2024, 5:14pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/2 "2024-06-29T17:14:55Z")
Great to see everything being brought up-to-date with the latest Debian, Asterisk, etc. Looking forward to try it out. One concern is that it appears all ASL2.0 bugs on github were today closed as ‘resolved’, yet they were not actually fixed, and then the repo was archived which seems to make it not possible to even see those issue reports any longer. Will those (app\_rpt) bugs need to be reopened in the ASL3 repo? ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [June 29, 2024, 5:32pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/3 "2024-06-29T17:32:44Z")
Yeah, we know. That was unexpected. It looks like maybe we can see those if we unarchive. I’m sure you can understand why we didn’t want to chase what might now be old bugs. We have been watching the ASL2 issues and have addressed many of them in ASL3. So give it a try and if you find a bug and don’t mind posting a new issue we’d appreciate it. ---
**Author:** ![AH6LE](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ah6le/32/1817_2.png) [@AH6LE](https://community.allstarlink.org/u/AH6LE)\ **Post date:** [June 29, 2024, 5:40pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/4 "2024-06-29T17:40:55Z")
Can existing .conf files be used or are there new parameters in 3.0? Migration is a concern ---
**Author:** ![WB6OZD](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/977dab/32.png) [@WB6OZD](https://community.allstarlink.org/u/WB6OZD)\ **Post date:** [June 29, 2024, 5:41pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/5 "2024-06-29T17:41:41Z")
This release is fantastic in every aspect! This is a must-have upgrade for any AllStar node. I’ve been running the beta on a 5 node PC install with several RTCM voters and also on a couple of hotspot versions on Pi’s and it is rock solid. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [June 29, 2024, 5:43pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/6 "2024-06-29T17:43:55Z")
> [@NR9V](#): > > One concern is that it appears all ASL2.0 bugs on github were today closed as ‘resolved’, yet they were not actually fixed, and then the repo was archived which seems to make it not possible to even see those issue reports any longer. Will those (app\_rpt) bugs need to be reopened in the ASL3 repo? As part of archiving the legacy code bases, GitHub recommends to close all outstanding issues which was done. To avoid confusion, I also hid that tab from the UI. However, for ASL-Asterisk, I’ve re-exposed the Issues here - [Issues · AllStarLink/ASL-Asterisk · GitHub](https://github.com/AllStarLink/ASL-Asterisk/issues?q=is%3Aissue). You should be able to see an issue you may have been concerned about. However, as Tim said, if you encounter an issue, a new issue should be raised with [app\_rpt](https://github.com/AllStarLink/app_rpt) (for Asterisk-related issues) or [ASL3](https://github.com/AllStarLink/ASL3) for just about anything else. The full suite of active GitHub repositories for AllStarLink v3 are: - ASL3 Tools - [GitHub - AllStarLink/ASL3: AllStarLink Version 3](https://github.com/AllStarLink/ASL3) - Asterisk app\_rpt Module - [GitHub - AllStarLink/app\_rpt: Refactoring and upgrade of AllStarLink's app\_rpt, etc.](https://github.com/AllStarLink/app_rpt) - ASL Menu - [GitHub - AllStarLink/asl3-menu: This repository contains the ASL3 menu system](https://github.com/AllStarLink/asl3-menu) - ASL Update Nodelist - [GitHub - AllStarLink/asl3-update-nodelist: systemctl timer based update-nodelist](https://github.com/AllStarLink/asl3-update-nodelist) - ASL Pi Appliance-Specific Issues - [GitHub - AllStarLink/asl3-pi-appliance: Non-Asterisk/app\_rpt Tools and Configuration for the ASL3 Pi Appliance](https://github.com/AllStarLink/asl3-pi-appliance) - DAHDI - [GitHub - AllStarLink/dahdi-linux: Dahdi Kernel Modules for Asterisk/ASL](https://github.com/AllStarLink/dahdi-linux) - ASL Manual - [GitHub - AllStarLink/ASL3-Manual: ASL Manual markdown for allstarlink.github.io](https://github.com/AllStarLink/ASL3-Manual) ---
**Author:** ![WB6OZD](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/977dab/32.png) [@WB6OZD](https://community.allstarlink.org/u/WB6OZD)\ **Post date:** [June 29, 2024, 5:44pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/7 "2024-06-29T17:44:57Z")
You’ll want to do it from scratch due to the changes in .conf file templating. See the explanation in the new online manual at [AllStarLink Manual](https://allstarlink.github.io/) I had a very large rpt.conf file for 5 nodes (voters & hubs) that was relatively easy to move to the new version. Now it is extremely easy to manage since so much of it no longer has to be repeated in the file. ---
**Author:** ![AH6LE](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ah6le/32/1817_2.png) [@AH6LE](https://community.allstarlink.org/u/AH6LE)\ **Post date:** [June 29, 2024, 5:48pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/8 "2024-06-29T17:48:00Z")
I read the docs but didn’t see anything about migrating to the new version. Crap, my node network is very complex… At least I can build it in a new Proxmox VM… ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [June 29, 2024, 5:50pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/9 "2024-06-29T17:50:27Z")
> [@AH6LE](#): > > I read the docs but didn’t see anything about migrating to the new version. Can you be more specific about what is complex about your configuration? We may be able to provide some recommendations on an efficient mirgration. ---
**Author:** ![AH6LE](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ah6le/32/1817_2.png) [@AH6LE](https://community.allstarlink.org/u/AH6LE)\ **Post date:** [June 29, 2024, 5:54pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/10 "2024-06-29T17:54:02Z")
I run 2 nodes on the same server, one private and one public. 20 different entries for the private nodes in my system and also have several iax and extensions entries for multiple users of DVSwitch as well. And that’s just my hub. I still have other remote sites to upgrade as well. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [June 29, 2024, 6:20pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/11 "2024-06-29T18:20:42Z")
> [@AH6LE](#): > > I run 2 nodes on the same server, one private and one public. 20 different entries for the private nodes in my system and also have several iax and extensions entries for multiple users of DVSwitch as well. Most of that should be easily copied-and-pasted into the new configuration. ---
**Author:** ![Buddy](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/b/e5b9ba/32.png) [@Buddy](https://community.allstarlink.org/u/Buddy)\ **Post date:** [June 29, 2024, 6:34pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/12 "2024-06-29T18:34:57Z")
Howdy, Two concerns. First, why couldn’t we use, for instance, Baline Etcher to image the SD card for a Pi? I tried the Raspberry Pi Imager, and it doesn’t read past the introductory screen with VoiceOver. That’s going to be a show stopper for me. Second, I assume if one wanted to build from source, one would just clone the git repository? No, I’ll forego building from source, probably. In any case, I’m glad to see this new version. I know it’s been something people have wanted for a long time, and I know it was a very complex undertaking. ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [June 29, 2024, 6:56pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/13 "2024-06-29T18:56:02Z")
> [@N8EI](#): > > Most of that should be easily copied-and-pasted into the new configuration. But be sure to understand the new Asterisk templets system. It will save you a TON of work in multi-node system. ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [June 29, 2024, 7:00pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/14 "2024-06-29T19:00:10Z")
> [@Buddy](#): > > Baline Etcher to image the SD card for a Pi? Because only the Raspberry Pi imager lets you create a hostname which you will merely point your browser at (ie myRpi5.local) without needing to know the IP address. Also, and more importantly, only the Pi imager lets you create a login user. Without doing that you WILL NOT be able to login to you Pi. ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [June 29, 2024, 7:02pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/15 "2024-06-29T19:02:40Z")
> [@Buddy](#): > > Second, I assume if one wanted to build from source, one would just clone the git repository? No, I’ll forego building from source, probably. We do provide all of our source at [AllStarLink, Inc · GitHub](https://github.com/AllStarLink) including instructions to compile from source should you become interested. ---
**Author:** ![Buddy](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/b/e5b9ba/32.png) [@Buddy](https://community.allstarlink.org/u/Buddy)\ **Post date:** [June 29, 2024, 8:09pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/17 "2024-06-29T20:09:26Z")
Howdy Tim, OK. The first thing I can absolutely get around without an issue. The second thing…yeah…definitely more of a problem. OK. Fortunately i don’t have to use the Mac. I’ll try the imager on a currently running Pi instead. Otherwise, I guess I might end up building from source after all. Which, hopefully, I can avoid. Vy 73, de KB5ELV ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [June 29, 2024, 8:14pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/18 "2024-06-29T20:14:39Z")
> [@Buddy](#): > > Fortunately i don’t have to use the Mac. I’ll try the imager on a currently running Pi instead. No Windows? There is a Windows version of the imager, too. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [June 29, 2024, 8:40pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/19 "2024-06-29T20:40:23Z")
> [@Buddy](#): > > First, why couldn’t we use, for instance, Baline Etcher to image the SD card for a Pi? Balena Etecher cannot set the required pre-imaging essential to the modern Raspberry Pi. You must use the Raspberry Pi imager. RPI Imager is supported on Windows, MacOS, and a number of Linux flavors. Is VoiceOver a screen-reader? ---
**Author:** ![K0KN](https://community.allstarlink.org/user_avatar/community.allstarlink.org/k0kn/32/1887_2.png) [@K0KN](https://community.allstarlink.org/u/K0KN)\ **Post date:** [June 29, 2024, 9:13pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/20 "2024-06-29T21:13:45Z")
Great News! Looking forward to giving it a try. Does this version solve the issue with multiple RF nodes on a single Raspberry Pi 4? 73 Kyle K0KN ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [June 29, 2024, 9:51pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/21 "2024-06-29T21:51:35Z")
Howdy Kyle, Yes, it does support multiple RF nodes. I have run USB + RTCM on a Pi3. I suspect it will do two simpleusb nodes w/o issue. Let us know how it works for you. [Next page](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241.md?page=2)