Image: ASL3 Diagnostic Check Command (Click on image for larger view.)
I recently experienced some issues where my 49355 ASL3 HUB node went offline for some rime or reason. The following issues were diagnosed:
- Configuration Conflict: The node was simultaneously running legacy IAX registration syntax and newer AllStarLink 3 (ASL3) HTTP API configuration blocks. This structural overlap threw a fatal error, preventing authentication.
- Systemd Startup Crash Loop: A system update introduced an incompatible high-priority flag (-p) into the systemd configuration wrapper. The underlying version of Asterisk rejected this flag, resulting in an immediate initialization failure (status=2/INVALIDARGUMENT), forcing the Asterisk process to repeatedly crash.
- HTTP Module Bypass: While ASL3 defaults to HTTP registrations, local software variables caused the Asterisk package on this specific machine to bypass the modern res_rpt_http_registrations.so engine entirely.
How was the above issues diagnosed? Looking at the three issues the task to get the node up and running look like a daunting one where I will have to write a complete new SD Card. Writing a complete new card and setting it up would have taken me several hours. No I did not make a backup - naughty, naughty me!
In my search around on how to find out what was the actual issues I found the following command to diagnose the node. I tried using Diagnostics Reports in the Cockpit but that returned - No System Reports. Well I found the following command: sudo asl-node-auth-check
What is the purpose of this command (sudo asl-node-auth-check) when using it to diagnose your AllStarLink3 Node?
The sudo asl-node-auth-check diagnostic script was introduced in AllStarLink 3 (ASL3) to address complex network environments. It automates the verification of your node's local configuration, registration, and end-to-end network path.
Here is a breakdown of what the tool evaluates when executed:
1. Holistic Configuration Audit
• Node Detection: Scans the active Asterisk environment to identify every node provisioned on the local machine.
• Conflict Resolution: Cross-references file parameters to detect mismatches or syntactic syntax conflicts between config files.
2. Deep Network Profile (IP & NAT Diagnostics)
• Multi-Location Testing: Performs concurrent tests over both HTTP and Inter-Asterisk eXchange (IAX) protocols against three geographically separate AllStarLink server locations.
• CGNAT Identification: By verifying network reach-ability from multiple external points, it definitively establishes if your node is trapped behind a Carrier-Grade NAT (CGNAT) or a restrictive mobile hotspot firewall.
• IP History Tracker: Displays information on the last time your node’s perceived public IP address changed.
3. Individual Node Authentication & Registration
• Syntax Validation: Checks that the local registration strings match the valid format mandated by the network.
• Port Verification: Confirms that the local port defined in your configuration exactly matches the database port assigned to you in the central registry database.
• Server Handshake: Tests actual routing and reach-ability directly to register.allstarlink.org.
• Staleness Tracking: Verifies if your node registration is active and current (checking that a valid database check-in has succeeded within the last 10 minutes).
4. Inbound IAX Reachability Test
• Parrot Routing System: Uses the newer central "Parrot/Reach-ability" system to simulate an incoming connection attempt to your node.
• Port Forwarding Proof: This tests if inbound traffic on your designated port can actually pierce your local router firewall and reach the node.
If your node has a green status on the AllStarLink Node List but cannot accept incoming connections, this utility isolates the fault.
As can be seen from the above this command is a very convenient way to diagnose issues your node might experience. Please note that is is a very powerful diagnostic command tool and one should use it with caution.
Here is the output of the command:
ZS1I@49355:~ $ sudo asl-node-auth-check
-----===== AllStarLink Node Authentication Check =====-----
Checking configuration:
Info: Skipping evaluation of private node 1961
Info: rpt.conf has configuration for: 49355
Info: /etc/asterisk/iax.conf contains 1 registration line(s)
Info: /etc/asterisk/rpt_http_registrations.conf contains no registration lines.
Info: Registrations present for configured node(s): 49355
Info: IP from https://conntest-east1.allstarlink.org/ip reports: xx.xxx.xxx.xxx
Info: IP from https://conntest-west1.allstarlink.org/ip reports: xx.xxx.xxx.xxx
Info: IP from https://conntest-west2.allstarlink.org/ip reports: xx.xxx.xxx.xxx
Info: IP from udp://conntest-east1.allstarlink.org:4570 reports: xx.xxx.xxx.xxx
Info: IP from udp://conntest-west1.allstarlink.org:4569 reports: xx.xxx.xxx.xxx
Info: IP from udp://conntest-west2.allstarlink.org:4569 reports: xx.xxx.xxx.xxx
OK: HTTP IP probes have consensus on the same perceived IP
OK: IAX IP probes have consensus on the same perceived IP
Testing node 49355:
OK: Node registration config is well-formed
OK: Node registration type is IAX
OK: register.allstarlink.org is reachable (via HTTP)
OK: IAX registration state is Registered
OK: Perceived IAX IP:PORT for this node is: xx.xxx.xxx.xxx:4569
OK: Registered to aws-east1a-register1.allstarlink.org - xx.xx.xxx.xxx
OK: Server-set UDP port matches bindport in iax.conf
OK: Node registration within 10 minutes: 2026-07-31 14:11:50 UTC
Info: Last time IP changed was 2026-07-29 09:48:32 UTC
OK: Incoming connections to IAX from other nodes is successful
Info: IAX ping test has a roundtrip time of 238ms
OK: No problems detected with node 49355
ZS1I@49355:~ $
xx.xxx.xxx.xxx - IP Addresses removed for obvious reasons.
Errors / Warnings will be reflected in the output of the command. From thereon you can fix the errors / omissions etc. As can be seen I experience three issues which was solved and the node is now running as it should. I also ensured that I made a paper format back-up of the current 49355 node setup as well as the back-up tool in sudo asl-menu.
I trust that this article might be of use to fellow radio amateurs that experience issues with an ASL3 node. This tool really "saved my bacon"!!




























