# I think I'm gong to give up on this **URL:** \ **Category:** AllStarLink\ **Tags:** new-users\ **Created:** [July 31, 2026, 5:26pm UTC](https://community.allstarlink.org/t/i-think-im-gong-to-give-up-on-this/24808 "2026-07-31T17:26:25Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![VE7BUL](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/d07c76/32.png) [@VE7BUL](https://community.allstarlink.org/u/VE7BUL)\ **Post date:** [July 31, 2026, 5:26pm UTC](https://community.allstarlink.org/t/i-think-im-gong-to-give-up-on-this/24808/1 "2026-07-31T17:26:25Z")
## I can usually figure out how to do what I want to do. This ASL3 with all the old misinformation (Youtube) and a manual that seems to jump around to other links has me baffled. I think I have the node configured okay for a radio to node. This is not what I had in mind. I did not bother to connect a radio as I wanted to establish a link first. I wanted to be able to access the radio from the internet. Laptop\>internet, internet\>node\>radio.... to repeater. I also wanted to be able to get the laptop internet through Starlink. I tried to set up IAXRpt on my Linux laptop, and it seems to run. I cannot make a connection to the node that works from IAXRpt. I occasionally get error messages depending on configuration in Allmon. Don't ask me what I'm doing, as I don't know. I have been beating my head against a wall for some time now, and I am at the point where I'm not sure if this exercise is worth it anymore. I see several places where IAXRpt is 'SO old'. I find it strange that there is not a Linux, or a Winblows application running under Linux, based dashboard that lets you control the radio functions. At this point, I'm pretty much done though. I am running Tailscale on both the node and the laptop, and that appears to be working okay. Maybe I'm wanting something that ASL is not capable of, I don't know. OS : Debian GNU/Linux 13 (trixie) OS Kernel : 6.18.34+rpt-rpi-v8 Asterisk : 22.9.0+asl3-3.9.3-1.deb13 ASL [app\_rpt] : 3.9.3 Installed ASL packages : Package Version ============================== ============================== allmon3 1.9.1-1.deb13 asl3 3.18-2.deb13 asl3-appliance 2.1.0-2.deb13 asl3-appliance-pi 2.1.0-2.deb13 asl3-asterisk 2:22.9.0+asl3-3.9.3-1.deb13 asl3-asterisk-config 2:22.9.0+asl3-3.9.3-1.deb13 asl3-asterisk-modules 2:22.9.0+asl3-3.9.3-1.deb13 asl3-menu 1.18-1.deb13 asl3-update-nodelist 2.0.0-1.deb13 asl-apt-repos 2.0-1.deb13 cockpit 337-1+deb13u1 cockpit-bridge 337-1+deb13u1 cockpit-networkmanager 337-1+deb13u1 cockpit-packagekit 337-1+deb13u1 cockpit-sosreport 337-1+deb13u1 cockpit-storaged 337-1+deb13u1 cockpit-system 337-1+deb13u1 cockpit-wifimanager 1.2.0-1.deb13 cockpit-ws 337-1+deb13u1 dahdi 1:3.1.0-2.1 dahdi-linux 1:3.4.0-11.asl.deb13 pi@Node68295:~ $ _Use `sudo asl-show-version` to obtain this information from the console or SSH_ Asterisk Version: 22..x.y+asl3-3.n.m ASL3 Version: 3.x.y ## Inquiry _See [https://allstarlink.github.io/user-guide/troubleshooting/](https://allstarlink.github.io/user-guide/troubleshooting/) on how to ask a good question to obtain the quickest and best assistance_ ---
**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 31, 2026, 7:04pm UTC](https://community.allstarlink.org/t/i-think-im-gong-to-give-up-on-this/24808/2 "2026-07-31T19:04:27Z")
> [@VE7BUL](#): > > I think I have the node configured okay for a radio to node. This is not what I had in mind. I did not bother to connect a radio as I wanted to establish a link first AllStarLink isn't a radio remote control system which is seems like that's what you're doing. I doesn't do remote radio control like a CAT or something - i.e. you're not going to change the channel, frequency, settings, etc. from ASL. You can use an AllStarLink node as simplex link to a repeater. The normal method for a simplex link like you're discussing is you setup a radio on the frequency of interesting with all of the particulars for the repeater you want to access. Make sure that all works first. Then you can use an IAX context to add an app to remotely key the attached radio. However this isn't a standard use case so there's no "one stop" directions for doing it. However, the gist is to setup a node as a normal simplex node and get that working first. The manual has step-by-step install directions and based on you calling it "node" I"m assuming you're using a Pi. [ASL3 Appliance Installation - AllStarLink Manual](https://allstarlink.github.io/install/pi-appliance/pi-detailed/). Then configure a separate IAX context for your application: [IAX Direct Authentication - AllStarLink Manual](https://allstarlink.github.io/adv-topics/iax-auth/). Be advised that using a direct IAX client is not very user friendly. There's a more modern all someone on the forum is developing that support Windows - [https://qso1.net/](https://qso1.net/). You still need a node with a radio setup though. ---
**Author:** ![W2DB](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/57b2e6/32.png) [@W2DB](https://community.allstarlink.org/u/W2DB)\ **Post date:** [August 1, 2026, 1:12pm UTC](https://community.allstarlink.org/t/i-think-im-gong-to-give-up-on-this/24808/3 "2026-08-01T13:12:22Z")
I read it that he's trying to connect to a link radio to a repeater. IAXRPT works great but you need to make sure the name and "secret" match, then point it at the right ip address and port. GeorgeC W2DB ---
**Author:** ![VE7BUL](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/v/d07c76/32.png) [@VE7BUL](https://community.allstarlink.org/u/VE7BUL)\ **Post date:** [October 9, 2026, 11:32pm UTC](https://community.allstarlink.org/t/i-think-im-gong-to-give-up-on-this/24808/4 "2026-10-09T23:32:43Z")
Picture QSO-One running way out in the bush, connected to the internet via Starlink. My home network, with a RPi and Allstar3, connected to a UHF Transceiver that can talk via RF to the local repeater UHF "HUB". The local repeater hub is a full duplex uhf repeater that handles multiple links and is connected to the local VHF drop repeater. Any traffic that goes into the hub is repeated and also goes out over the VHF repeater. Any traffic going into the VHF repeater is also sent out over the UHF hub. All I need is to be able to connect and talk through my home transceiver, from a remote location using Starlink and Allstar. The manual jumps around so much I cannot keep up and it puts me to sleep. I find this very frustrating, to put it mildly. If there are clear and concise instructions on how to do this, I would appreciate being made aware of the where and how to. Thanks for any assistance. 73 de Gil ve7bul. ---
**Author:** ![N7GT](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n7gt/32/5247_2.png) [@N7GT](https://community.allstarlink.org/u/N7GT)\ **Post date:** [October 11, 2026, 12:08am UTC](https://community.allstarlink.org/t/i-think-im-gong-to-give-up-on-this/24808/5 "2026-10-11T00:08:06Z")
Gil, I agree with you 100%. I have been struggling with this for weeks, and after a lot of bad advice I got a response from David Gleason, @NR9V. His suggestion was spot-on, but I continue struggling with the configuration. I am a Windows person, and know absolutely zilch about Linux/Debian. Without specific step-by-step instructions, I am completely in the dark. I got Debian and Allmon3 installed; setup port forwarding as noted in the instructions; but, according to CLI, my internet traffic "passes" but I still not able to get my node to register with Allstar. I have searched and search, read and re-read, pages upon pages in the Community and other Forums. It says "do this" but never says "how to do it." I wish there was a live tech-support that someone could remote into my computer and walk me through the steps. I had a desire to learn this stuff, but the frustration factor has got me to the point, like you, where I want to toss in the towel and scrap this entire project. Wish you luck, my friend! ---
**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:** [October 11, 2026, 12:41am UTC](https://community.allstarlink.org/t/i-think-im-gong-to-give-up-on-this/24808/6 "2026-10-11T00:41:08Z")
AllStarLink is an open source product manned entirely by volunteers and we don't charge for the system. This includes writing the documentation and we get very few volunteers to help write documentation. The documentation is also pretty clear that you need some basic Linux understanding for anything except the default setup. There are several vendors to whom you can pay a premium to for their hardware and a bespoke configuration assistance. Threads complaining about things being hard without asking questions or providing any troubleshooting information can't really be serviced. ---
**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:** [October 11, 2026, 12:41am UTC](https://community.allstarlink.org/t/i-think-im-gong-to-give-up-on-this/24808/7 "2026-10-11T00:41:36Z")