Thanks,
Bob
KE0SDV
If you have access to another all star link node, goto var/lib look for rpt_extnodes.
Find your node number 56517 the public ip address will be there use that to access the node.
Which is 67.43.211.214
Yes asnode.org and node.allstarlink.org are not working
asnode.org is not an AllStarLink service and has been down for weeks. AllStarLink nodes have the format nnnnn.nodes.allstarlink.org which works just fine:
$ dig +short 56517.nodes.allstarlink.org
67.43.211.214
There is no need to look in the legacy rpt_extnodes file. It's very possible you're behind a CGNat that has now split its IP addressing. Unfortunately since you're on a legacy HamVOIP system, the tool to determine that is not available.
HamVOIP has a similar node resolution tool but for the life of me I can't remember it. I've been googling it for a while and can't phrase the question in such a way that the A. I. doesn't get in the way and give wrong answers. Anyway you could also get a dynyns account and put a tool on your pi to have a second or third way to find it. That could also be put in your router if you want your home devices to be findable.
HamVOIP does not have ASL3's asl-node-auth-check to determine all sorts of things, including if your node reports different IP addresses from different parts of the internet. This is indicative of CGNAT which basic DNS resolution based on registration cannot tell you.
Thank you for the info… I stand corrected.
OP did state is was able to connect in the past… seeing the ip number belongs to Vistabeam a wireless internet for rural customers and wired for in larger cities business connections, more than likely if he is on wireless connection went to a CGNAT system he will not be able to ssh to it unless he can install a vpn port forwarding service on the node.
Yes, most likely it's CGNAT. 44Net Connect using Wireguard is the current solution:
Planning is underway to deal better with CGNAT issues but it's a big change that will abandon a lot of legacy system users.
HamVoIP's lookup domain is ip.hamvoip.org. So node-number.ip.hamvoip.org.
They also have a registration server that operates in parallel to ASL. Don't know if anyone still uses that, and there's no reason why anyone should.
Don't use that as a reference, though, because unregistered node numbers stay cached forever until updated.
As mentioned previously, HamVoIP doesn't have asl-node-auth-check, which is useful for diagnosing connection issues.
I think the solution is going to involve the CGNAT system. Our repeater shack is on the side of a mountain on the property of one of our members. When I installed the Hamvoip node in 2022 we had problems with the ISP, a fixed wireless installation serving several homes on the mountain. At the time I had to have the ISP open some ports. It then worked using 56517.asnode.org. I had not tried to SSH into the node for many months. The ISP was also sold to a new provider sometime in the last couple years. It is possible they have closed the port(s) I need open. From home I cannot SSH into the node using any method, including the public IP address and 56517.nodes.allstarlink.org and 56517.ip.hamvoip.org. I can SSH into the node from a Windows computer at the repeater shack on the same network as the Hamvoip node. Is there a way to query the upstream CGNAT system to find out which ports it has open to our repeater shack? Note: The owner of the home where our shack is located also gets his internet service from the same ISP. I can contact the ISP but it would be helpful to know in advance how it's CGNAT system is configured.
ASL isn't compatible with CGNAT. The reason being is your IP will be different every time to talk to someone else based on session or geographic location or anything. The best you could hope for is to contact the ISP and see if you can have a fixed IP or at least a public IP that doesn't change.
I confirmed with my ISP that it is under CGNAT. They are going to issue a fixed public IP address to me next week. Sometime last year the local fixed wireless ISP I was using was sold to Vistabeam and they set me up under CGNAT. I'm surprised that anything on my Allstarlink node worked after that, especially the inbound connection to Echolink. Since the node was working for basic activities like top-of-the-hour repeater messages, I never tried to do any maintenance or other inbound connections that now don't work. Anyway, I will report back after I get the fixed IP address. Sidenote: I'm going to build an ASL3 node to replace this one when I get time.
Bob
KE0SDV
Node 56517
My ISP has given me a fixed public IP address that doesn't change. I think it is 67.43.211.214, but not sure. So far I haven't been able to make it work. This is for my node 56517. Can you confirm my public IP address? The router still has the same port forwarding. What do I need to change in my node or router to make it work?
Bob
% asl-node-lookup 56517
SRV (_iax._udp.56517.nodes.allstarlink.org)
10 10 4568 56517.nodes.allstarlink.org.
A (56517.nodes.allstarlink.org)
67.43.211.214
TXT (56517.nodes.allstarlink.org)
NN=56517
IP=67.43.211.214
PT=4568
I got a static IP address from my ISP. Everything is working now, including remote access.
Thanks,
Bob