Can't Connect To MY Node

AllStarLink
1

Setup Information

Use sudo asl-show-version to obtain this information from the console or SSH

I’ve been having difficulties lately connecting to my AllStar Node “64828”.

I’ve tried several methods but to no avail.

Here is a dump from my ssh interface:

admin@node64828:~ $ dig txt +noall +answer 64828.nodes.allstarlink.org

admin@node64828:~ $

The second and third attempts are to my node (64828), which gets no response.

All port forwarding settings through my router are set correctly.

Before I attempt to reload the software on my Pi, I thought I would reach out and see if there is anything that you guys can see that I am doing incorrectly.

Thanks,

-tp

Asterisk Version: 22..x.y+asl3-3.n.m
ASL3 Version: 3.x.y

********** AllStarLink [ASL] Version Info **********

OS : Debian GNU/Linux 12 (bookworm)
OS Kernel : 6.12.47+rpt-rpi-2712

Asterisk : 22.5.2+asl3-3.6.3-1.deb12
ASL [app_rpt] : 3.6.3

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.6.1-1.deb12
asl3 3.11-1.deb12
asl3-asterisk 2:22.5.2+asl3-3.6.3-1.deb12
asl3-asterisk-config 2:22.5.2+asl3-3.6.3-1.deb12
asl3-asterisk-modules 2:22.5.2+asl3-3.6.3-1.deb12
asl3-menu 1.15-1.deb12
asl3-pi-appliance 1.10.1-1.deb12
asl3-update-nodelist 1.5.1-1.deb12
cockpit 287.1-0+deb12u3
cockpit-bridge 287.1-0+deb12u3
cockpit-networkmanager 287.1-0+deb12u3
cockpit-packagekit 287.1-0+deb12u3
cockpit-sosreport 287.1-0+deb12u3
cockpit-storaged 287.1-0+deb12u3
cockpit-system 287.1-0+deb12u3
cockpit-wifimanager 1.1.1-1.deb12
cockpit-ws 287.1-0+deb12u3
dahdi 1:3.1.0-2
dahdi-dkms 1:3.4.0-10.asl.deb12
dahdi-linux 1:3.4.0-10.asl.deb12
dahdi-source 1:3.4.0-10.asl.deb12

2

Your node hasn't been registered since 2025-12-24. You can see that at Searchable Node List.

3

I have reloaded ASL and it show registered, but I still can’t connect to it.

Thoughts?

4

Looks like it registered once about 7 hours ago. How are you determining it's currently registered?

5

I viewed the AllStar page and it showed it was up.

6

Do you mean Searchable Node List? According to this, your node hasn't been seen since 2025-12-28 19:46 UTC (currently 2025-12-29 00:25 UTC as I write).

7

Yea, I’ve just about given up on Allstar as it become far to complicated to configure properly.

-tp

8

Are you using a clean install and asl-menu to do the configuration? It's very straight forward for most cases. Are you on any sort of oddball Internet?

9

Yes, I’ve tried reinstalling Allstar several times. I am using a Pi-Hole server but I have also tried taking it out of the system to test using nothing more than the dedicated dns of xfinity. I’m also not able to ping “register.allstarlink.org” from the asl menu but am able to ping google. I’ve even tried pinging it from a separate computer using a cellular connection and still no ping. Are you able to ping it? I honestly don’t know was has happened as AllStar worked just fine for months even using my PiHole. Have you tried installing it from scratch using existing resources to see if it still works for you that way?

10

The pinging of register.allstarlink.org is an unfortunate timing issue in the menu with the update of the registration system that occurred back in October. That check is being replaced with a webserver test but that code is not yet promoted to production/main yet. See (asl-menu : replace "Ping register.allstarlink.org" by Allan-N · Pull Request #99 · AllStarLink/asl3-menu · GitHub).

However, ability to ping isn't a sign of registration. Assuming you're using a stock ASL (which does work fine) what does the output of rpt show registrations yield? You should see a state "Registered". It currently, as of this time (2025-12-29 18:37 UTC) showing a registration time of 18:33 which is in the 600 second window of "registered".

You appear to have 64828 marked as a remotebase which means your DNS will be 64828.remotebase.nodes.allstarlink.org. If your node isn't actually setup as a remotebase, you should undo that in the portal for that node.

11

If it is that your node is remote base, know that it can only allow ‘one connect’.

So, if you have any, even a private node connected to it, that is all you get.

Change remote base designation if it is not. It is really a security feature and nothing to do with the idea that it is a freq agile remote or even a simple remote. Which it can be without the designation.