Asl-node-auth-check question

AllStarLink
1

What does:
OK: Node registration config is well-formed
OK: Node registration type is HTTP
OK: register.allstarlink.org is reachable (via HTTP)
OK: HTTP registration state is Registered
OK: Perceived IAX IP:PORT for this node is: 136.49.198.155:4180
OK: Registered to aws-east1a-register0.allstarlink.org - 52.20.63.146
OK: Server-set UDP port matches bindport in iax.conf
OK: Node registration within 10 minutes: 2026-04-09 05:31:56 UTC
Info: Last time IP changed was 2026-03-30 15:56:42 UTC
Warning: Node is not perceived as registered; not tested

indicate from asl-node-auth-check ?

2 
    OK: Node registration config is well-formed
    OK: Node registration type is HTTP
    OK: register.allstarlink.org is reachable (via HTTP)
    OK: HTTP registration state is Registered
    OK: Perceived IAX IP:PORT for this node is: 136.49.198.155:4180
    OK: Registered to aws-east1a-register0.allstarlink.org - 52.20.63.146
    OK: Server-set UDP port matches bindport in iax.conf
    OK: Node registration within 10 minutes: 2026-04-09 05:56:03 UTC
  Info: Last time IP changed was 2026-04-09 05:07:51 UTC

Warning: Node is not perceived as registered; not tested

3

I have a similar report, but when I un commented in iax.conf the registration, it didn’t like having duplicate registration with rpt_http_registrations.conf

4

What version of the asl3 package do you have? dpkg -l asl3?

5

You don't want or need duplicate registrations like that. That's why the script tells you to resolve it.

6

If you have a version of the asl3 package that is earlier than, 3.17, please do the following to get the latest version as there are several parsing fixes for weird configuration syntax:

sudo wget -O/usr/bin/asl-node-auth-check https://repo.allstarlink.org/hotfix/asl-node-auth-check
sudo chmod 755 /usr/bin/asl-node-auth-check
sudo /usr/bin/asl-node-auth-check
7

dpkg -l asl3

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii asl3 3.15-1.deb12 all AllStarLink 3

with latest version asl-node-auth-check I still get:

    OK: Node registration config is well-formed
    OK: Node registration type is HTTP
    OK: register.allstarlink.org is reachable (via HTTP)
    OK: HTTP registration state is Registered
    OK: Perceived IAX IP:PORT for this node is: 136.49.206.123:4180
    OK: Registered to aws-east1a-register0.allstarlink.org - 52.20.63.146
    OK: Server-set UDP port matches bindport in iax.conf
    OK: Node registration within 10 minutes: 2026-04-09 14:28:52 UTC
  Info: Last time IP changed was 2026-04-09 08:14:46 UTC

Warning: Node is not perceived as registered; not tested

8

Interesting. That's telling you that the nodeping remote service doesn't perceive you as registered but that isn't matching the other state. What node specifically are you testing?

9

It’s a new build of 46715. This has been running on ASL2 beta along with a P25 reflector and a P25 analog bridge. I want to make sure the ASL3 side is working properly before I install any DVSwitch stuff.

10

Okay, I see what's happened here. In fixing another issue, I'm triggering the wrong error message for your case. What you're running into is that your system node isn't responding on UDP port 4180. I'll need to fix this in asl-node-auth-check. I'll poke at it tonight and get a new hotfix up for you to try. But your issue is that UDP/4180 isn't working inbound to your node.

11

Specifically:

https://nodeping.allstarlink.org/?node=46715

{"calleraddr":"127.0.0.1","ipv4":{"rc":-9,"status":"unreachable"},"version":"20260303.0"}

vs.

https://nodeping.allstarlink.org/?node=2000

{"calleraddr":"127.0.0.1","ipv4":{"addr":"18.224.69.177","pingms":11,"port":4569,"rc":0,"status":"ok"},"version":"20260303.0"}
12

I also have a similar DMR node on 409873. This one doesn’t throw the warning/error. I’m thinkiing they should both behave similarly. Also, please keep in mind that 46715 doesn’t you have any DVSwitch stuff installed. It should be ASL3 good. What could be different in my installation?

13

So those nodes are at the same IP but on different ports. 46715 is setup in the portal to be on UDP/4180 and you have 409873 configured to be on UDP/4550. Are these on the same system? If so, you need to align both nodes to use the same UDP port or do a NAT forward from 4180 to 4550. If these are on two different systems entirely than either you have the local firewall not properly configured on the ASL3 system (assuming you're using the appliance) or it's not NATing correctly.

14

doesn’t yet have any . . . . not doesn’t you have any

15

Those nodes are on separate Pi’s on different LAN IP’s and different ports. ‘Not connect in any way. The point is that they are similar in that they use rxchannel = USRP (in rpt.conf), because of the DVSwitch interface.

16

You're missing my point... this is about the port configured in iax.conf or in your firewall. It's not an ASL issue.

17

Testing node 46715:
OK: Node registration config is well-formed
OK: Node registration type is HTTP
OK: register.allstarlink.org is reachable (via HTTP)
OK: HTTP registration state is Registered
OK: Perceived IAX IP:PORT for this node is: 136.49.132.79:4180
OK: Registered to aws-east1a-register2.allstarlink.org - 52.44.147.201
OK: Server-set UDP port matches bindport in iax.conf
OK: Node registration within 10 minutes: 2026-04-09 18:43:47 UTC
Info: Last time IP changed was 2026-04-09 18:40:44 UTC
OK: Incoming connections to IAX from other nodes is successful
Info: IAX ping test has a roundtrip time of 33ms
OK: No problems detected with node 46715

ALL GOOD NOW! ‘Firewall issue – TNX AGN!