# 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:** 3
**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 30, 2024, 5:25pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/42 "2024-06-30T17:25:47Z")
> [@N0NB](#): > > I’d appreciate a pointer to where the custom settings are stored just to verify them prior to the first boot. Rapsberry Pi OS “firstboot” configures all of that during, well, firstboot. The imaging process writes the customizations to the vfat partition where `/boot` lives in various places. Those are then applied as the system starts. You can’t unpack/inspect the ext4 root system for proper configuration until after the firstboot process. ---
**Author:** ![KC0CAP](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/e56c9b/32.png) [@KC0CAP](https://community.allstarlink.org/u/KC0CAP)\ **Post date:** [June 30, 2024, 5:44pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/43 "2024-06-30T17:44:31Z")
OK, ya I’m punting here. But I’m using the web admin portal and then terminal and the menu , then expert config menu and then trying to edit in there. I have also tried using putty and get the file to open and edit but never able to save. ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [June 30, 2024, 6:01pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/44 "2024-06-30T18:01:16Z")
> [@KC0CAP](#): > > OK, ya I’m punting here. But I’m using the web admin portal and then terminal and the menu , then expert config menu and then trying to edit in there. I have also tried using putty and get the file to open and edit but never able to save. First off, it would be good to know which editor you selected. Since you have been using asl-menu and the expert config menu you should have been asked which editor you would like to use (with the default being nano). You can get back to this menu using “`sudo select-editor`”. Assuming that you are using “nano” you will see a legend at the bottom of the screen. When you see sequences like “^X” that means control-X (hold down the control key and type “X”). To save a file you would use “^O” (control-O) to “Write Out” the file. That should bring up a “File Name to Write:” line just above the legend with the name of the file you are editing being displayed. Since you want to write the same file you can simply hit the Return/Enter key. That should have saved the file with any updates you made. If you are finished with the file then you would use “^X” (control-X) to “Exit”. I hope this helped. ---
**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 30, 2024, 6:56pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/45 "2024-06-30T18:56:00Z")
Chip, Thank you so much for saying that. ---
**Author:** ![dwarnok](https://community.allstarlink.org/user_avatar/community.allstarlink.org/dwarnok/32/2160_2.png) [@dwarnok](https://community.allstarlink.org/u/dwarnok)\ **Post date:** [June 30, 2024, 8:28pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/46 "2024-06-30T20:28:18Z")
You say “Let us know what you think”, so I think ASL would be much improved if it were open-source with compilable code. Introducing a Linux OS to others is difficult for you, but there are many node operators who live daily with Unix/Linux. ---
**Author:** ![vk3jed](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/c2a13f/32.png) [@vk3jed](https://community.allstarlink.org/u/vk3jed)\ **Post date:** [June 30, 2024, 8:39pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/47 "2024-06-30T20:39:21Z")
> Yeah, that’s a todo. I recall an outside contributor posted a docker compose yaml. For ASL3? I know several attempts were made to containerise previous versions, but all failed. From memory, DAHDI was the main issue. If there is a Dockerfile and yaml for ASL3 that works, I’d be happy to have a play. ---
**Author:** ![Tom](https://community.allstarlink.org/user_avatar/community.allstarlink.org/tom/32/3049_2.png) [@Tom](https://community.allstarlink.org/u/Tom)\ **Post date:** [June 30, 2024, 8:40pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/48 "2024-06-30T20:40:32Z")
ASL3 is a huge improvement and that significant effort is much appreciated. Where can I set static IPs? What’s the best way to turn on/off WLAN access? Thanks again, Tom / K5TRA ---
**Author:** ![vk3jed](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/c2a13f/32.png) [@vk3jed](https://community.allstarlink.org/u/vk3jed)\ **Post date:** [June 30, 2024, 8:43pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/49 "2024-06-30T20:43:14Z")
> It’s theoretically possible to run it in Docker and Podman. It requires some setup for the `/dev` entries and exposing the kernel models needed to the docker. What we really need is a container wizard to help with the project - would make some of these kinds of features go much faster. In my case, I don’t need audio devices, as the system in question is a hub (actually multiple hubs). My container foo isn’t quite up to exposing kernel modules yet. 😃 I’ll need someone else to do that side of things. 🙂 ---
**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 30, 2024, 8:47pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/50 "2024-06-30T20:47:46Z")
Most OS settings are done with Cockpit, IP address included. [![](https://community.allstarlink.org/uploads/default/original/2X/d/de8e5d1042a589ca7a09d8e3a0279cab16bcc8d3.jpeg "STATIC IP ADDRESSES on ASL3 AllStarLink") ](https://www.youtube.com/watch?v=593q7CbPKSQ) Also see [Network Configuration - AllStarLink Manual](https://allstarlink.github.io/pi/cockpit-network/) ---
**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 30, 2024, 9:13pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/51 "2024-06-30T21:13:17Z")
> [@dwarnok](#): > > You say “Let us know what you think”, so I think ASL would be much improved if it were open-source with compilable code. Introducing a Linux OS to others is difficult for you, but there are many node operators who live daily with Unix/Linux. I’m not sure I’m following what you are trying to say here. All of AllStarLink v3 **IS** open source code. Look above and I posted the links to all of the various GitHub repositories that contain the code and how to raise issues with the different compents. One can also build their own system and install ASL3 on it without the Pi appliance elements. It’s all documented in [the manual](https://allstarlink.github.io). ---
**Author:** ![KE6PCV](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ke6pcv/32/429_2.png) [@KE6PCV](https://community.allstarlink.org/u/KE6PCV)\ **Post date:** [June 30, 2024, 11:12pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/52 "2024-06-30T23:12:51Z")
There is always someone who doesn’t know all the facts and is quick to complain! ---
**Author:** ![dwarnok](https://community.allstarlink.org/user_avatar/community.allstarlink.org/dwarnok/32/2160_2.png) [@dwarnok](https://community.allstarlink.org/u/dwarnok)\ **Post date:** [July 1, 2024, 12:10am UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/53 "2024-07-01T00:10:11Z")
It seems “make” doesn’t compile included code, but downloads and installs it. It’s also of concern here that there is no “uninstall” option in Makefile. ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [July 1, 2024, 12:49am UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/54 "2024-07-01T00:49:30Z")
> It seems “make” doesn’t compile included code, but downloads and installs it. I am not sure which “make” you are referring to but, yes, the build process does include a few downloads (most importantly, we need the asterisk source code). The build steps pull together the various pieces (asterisk, app\_rpt), apply a few needed patches, and then you have a directory with all of the bits to compile. Is this a bit complicated? Yes. Do we have our reasons for doing things this way. Yup. > It’s also of concern here that there is no “uninstall” option in Makefile. Umm, the asterisk source code’s top-level Makefile HAS an “uninstall” option. ---
**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\ **Post date:** [July 1, 2024, 7:57am UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/55 "2024-07-01T07:57:50Z")
Amazing update. Hard to believe they kept it under wraps. I got it set up on a new node fast- but when installing AllScan ran into a problem that looks like the AllScan updater does not run on x64bit. I have not seen any info in ASL guides, wiki, AllScan info, etc saying the OS must be x32bit. Am I dead in the water and must start over with x32bit ISO? Thx. ---
**Author:** ![Bretteld74](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/b/b5ac83/32.png) [@Bretteld74](https://community.allstarlink.org/u/Bretteld74)\ **Post date:** [July 1, 2024, 11:57am UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/56 "2024-07-01T11:57:27Z")
Hello guys can you use dvswitch with the new asl3. Is installation different compared to previous asl. thanks Brett VK4BDE ---
**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:** [July 1, 2024, 12:12pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/57 "2024-07-01T12:12:21Z")
> [@KK6QMS](#): > > Am I dead in the water and must start over with x32bit ISO? AllScan is supported on ASL3 by its author: [https://github.com/davidgsd/AllScan?tab=readme-ov-file#release-notes](https://github.com/davidgsd/AllScan?tab=readme-ov-file#release-notes). ASL3 does not support 32-bit operating systems. ---
**Author:** ![PD0SBH](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/p/c5a1d2/32.png) [@PD0SBH](https://community.allstarlink.org/u/PD0SBH)\ **Post date:** [July 1, 2024, 12:55pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/58 "2024-07-01T12:55:48Z")
Hello all, Thanks for the amazing update, kudo’s to all who contributed to this, really nice work! One thing I ran into on the otherwise very smooth setup is the connpgm (and discpgm) programs. However I put these options into the rpt.conf file, template section or general part I cannot seem to get this to work. Even just a simple touch of a file in /tmp doesn’t seem to get executed. Have I missed something in the extensive (again kudo’s) documentation about changes to this option for ASL3? Thanks, 73, Max ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [July 1, 2024, 1:21pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/59 "2024-07-01T13:21:14Z")
> [@PD0SBH](#): > > One thing I ran into on the otherwise very smooth setup is the connpgm (and discpgm) programs. However I put these options into the rpt.conf file, template section or general part I cannot seem to get this to work. Even just a simple touch of a file in /tmp doesn’t seem to get executed. Have I missed something in the extensive (again kudo’s) documentation about changes to this option for ASL3? I just configured a simple connpgm (and discpgm) and all worked … for me. So, let’s start with the simple things like making sure your pgm’s are executable (chmod +x …) and have been tested independently. Also, you need to remember that the asterisk process is no longer running as “root”. Any files that you are reading/writing need to be accessible to the “asterisk” user. Oh, wait, maybe this is NOT working. Investigating … and it looks like you have found a real bug. I will file a GitHub issue and we’ll see if we can get that fixed. … and a fix is coming. Just give us some time to turn the cranks and push out an update. ---
**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:** [July 1, 2024, 5:02pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/60 "2024-07-01T17:02:32Z")
What aspect of “dvswitch” are you asking about? If you mean DVSwitch Mobile, yes it works fine and there will be some configuration differences. ---
**Author:** ![K6JWN](https://community.allstarlink.org/user_avatar/community.allstarlink.org/k6jwn/32/2265_2.png) [@K6JWN](https://community.allstarlink.org/u/K6JWN)\ **Post date:** [July 1, 2024, 5:06pm UTC](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241/61 "2024-07-01T17:06:21Z")
Congrats to the team! I know this was a huge project to tackle and great to see it out in the wild! I plan on upgrading my nodes over the next few weeks! Keep up the good work! Jim, K6JWN [Previous page](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241.md?page=2) [Next page](https://community.allstarlink.org/t/check-out-the-asl3-announcement/21241.md?page=4)