Monday evening I was part of a show and tell about Allstar. My node performed just fine. Since I had to reinstall it locally, when debian 12 came up I ran the apt update and apt upgrade sequence. After a reboot I’ve been unable to connect (using Allmon3, Allscan, dtmf) other than to the 55553 parrot. This is what I see in asterisk: trying two different nodes (a repeater and a hub) I’ve easily connected to in past times.
Yes, I’ve been through the steps nicely outlined in the five connection issues posted in late 2024 and still no joy. I’ve spent a day on it now and I’m about spent. The debian 12 (on intel) installation of ASL3 has been rock solid for many months.
If you can only connect to 55553 then there is something wrong with your registration. 55553 accepts all connections and doesn’t care if your registration is invalid. Typical nodes only allow nodes with valid registrations to connect.
Thanks. When I looked at the portal it kept saying it was registered so I didn’t do the rpt show regs. I’m not sure why the local instance didn’t connect to the server which Whois tells me is in Chicago, until I deleted and recreated the entry in the portal. And why is my host showing as this address rather than my local debian instance. I’m guessing the “Host” is the “Allstarlink host”
I have two backhauls here and I see the node is switching between them though the “Host” ip hasn’t changed. I think I’ll nail the node to a single backhaul.
Yes, in the rpt show registrations output the Host column shows the server your node registered with. The Perceived column shows the IP address that made the registration request.