I have nodes 618030, 618033, 618034 and 618035 running at the moment.
618035 is ASL 3 on Debian 12 running as a hub only and appears to be good at the moment - its on a connection at my workshop. 618033 is Hamvoip at a repeater site, and that one appears to be good, its connected to 618035. 618035 hub is connected to 59606.
Nodes 618030 and 618034 are also HamVoip running on my home network, and they cant establish outbound connections. I got this list https://snodes.allstarlink.org/diffnodes.php and the two failing nodes dont appear in there.
These home nodes started failing after I created a Wireguard VPN to my workshop, so its most likely my fault. To help diagnose the problem I have completely disabled Wireguard both locally and at the workshop.
I can ping register.allstarlink.org from the failing nodes, so I'm confused as to why they are not registering.
No changes were made to to the nodes that are failing, only to the router on their network. The reason I created the VPN was to test Allmon3 on the ASL3 node 618035 to save myself a trip to the workshop. The VPN has been disabled on the router now, as I don't need it any more. Node traffic was never intended to go over the VPN, but due to a config error I think that's what happened. To me it seems as though the registration server doesn't like the two nodes that are failing.
That will show me what my nodes local IPs are, but they are behind NAT, so the registration server will see my public static IP.
I think what I have inadvertently done is route these two nodes through my Wireguard and they have came out on my workshop public IP and confused the registration server.
It does appear as though the nodes are reporting now, but they don't appear in the node list yet..
When you suggested to check what the server thinks my IP is, I thought you meant the registration server rather than my node server.
No, sorry, I was having a phone convo with my out of state bro while I was answering you.
Did not come out very clear.
Not sure if this will help you with hamvoip but
systemctl restart updatenodelist
That would force the node list updater to restart in the older asl in the case it stalled.
The nodes are still not reg'd but you may have them down.
from a system prompt, you can curl ifconfig.me to get your wan ip
But perhaps it is a dns issue now ?
You might try to switch back to dhcp for a test, but backup your old config first.
Connect out only because the port forwarding will not match for inbound.
Make sure you wait a few minutes for the node list to catch up to you if it reg's.
Ive changed the internal IP of the node, I've tried registering a spare node number 618031, I've restarted the router again, and both the failing nodes and still no joy..
I'm co-admin on the VKLink network which also uses app_rpt,. We have the option to report to both AllStarLink and VKLink servers. I configured 618030 to report to VKLink also, and it did so quite happily. I logged in to the admin console to see what IP address the VKLink server thought my public IP is, and its correct. I'm even more out of ideas now..
There are no nodes on the same server. 618030 and 618034 are each on their own Pi 3B+, but both on the same LAN behind the same NAT, and both are failing. Each run the HamVoip image - I'm not sure how HamVoip does its ASL registration, but however it is out of the box after you follow the prompts to setup..