Registration errors from behind a VPN

Greetings:

I feel kind of stupid today.

I'm helping someone set up a node on T-Mobile home internet. They have a VPS, through which the node is tunneling through a Wireguard configuration. I've done this at least a dozen times, and this one is new.

The node appears to be registering, but is not perceived as registered. Not sure what the difference is, or what is supposed to be perceiving the node as registered.

Anyway, here's output from asl-node-auth-check.

-----===== AllStarLink Node Authentication Check =====-----

Checking configuration:
Info: rpt.conf has configuration for: 63730
Info: /etc/asterisk/iax.conf contains no registration lines.
Info: /etc/asterisk/rpt_http_registrations.conf contains 1 registration line(s)
Info: Registrations present for configured node(s): 63730
Info: IP from https://conntest-east1.allstarlink.org/ip reports: 172.234.205.87
Info: IP from https://conntest-west1.allstarlink.org/ip reports: 172.234.205.87
Info: IP from https://conntest-west2.allstarlink.org/ip reports: 172.234.205.87
Info: IP from udp://conntest-east1.allstarlink.org:4570 reports: 172.234.205.87
Info: IP from udp://conntest-west1.allstarlink.org:4569 reports: 172.234.205.87
Info: IP from udp://conntest-west2.allstarlink.org:4569 reports: 172.234.205.87
OK: HTTP IP probes have consensus on the same perceived IP
OK: IAX IP probes have consensus on the same perceived IP

Testing node 63730:
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: 172.234.205.87:4569
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-07-19 19:17:12 UTC
Info: Last time IP changed was 2026-07-19 18:19:03 UTC
Warning: Node is not perceived as registered; not tested

Warning: Node 63730 has 1 warning(s)!
Warning: Warnings may or may not be problems depending on configuration

And here is output from rpt show registrations.

Host Username Perceived Refresh State
52.20.63.146:443 63730 172.234.205.87:4569 179 Registered
1 HTTP registration

Password has been checked and verified. Also tried IAX registration.

What am I missing?

73

N2DYI

Looks like there's a bug in parsing the output of the nodeping status. It should be reporting "Incoming connections to IAX from other nodes failed; client IP or firewall issue." You can see this yourself at https://nodeping.allstarlink.org/?node=63730. Looks like you have an IAX port issue.

Oh, good. That I can deal with, but the output confused me.