Nodes KN6BDW 51879 and KN6DPT 51865. 51879 does not have UDP port forwarding, 51865 supposedly does. 51879 can sometimes connect to 51865, maybe 50% of the time.
Just FYI, the Allstarlink, Inc registration servers are working fine. No issues.
I noticed that you are using the command “rpt lookup (node number)”
That certain command is not available in the app_rpt open source CLI prompt.
It appears that this command does work in CLI prompt from closed source HamVOIP software, I am not sure where the data comes from.
It may be their attempt at a registration server and it is not working properly on node 51879.
Just a guess.
73
Marshall - ke6pcv
···
From: Gerry Filby via AllStarLink Discussion Groups [mailto:noreply@community.allstarlink.org] Sent: Thursday, June 18, 2020 4:34 PM To:ke6pcv@cal-net.org Subject: [AllStarLink Discussion Groups] 2 nodes having problems connecting to each other
Nodes KN6BDW 51879 and KN6DPT 51865. 51879 does not have UDP port forwarding, 51865 supposedly does. 51879 can sometimes connect to 51865, maybe 50% of the time.
These nodes are registering with the ASL servers, not HamVoIP.
How much time had elapsed from the point node 51865 was brought on-line to the point where the
“rpt lookup 51865” was run from node 51879? I’m suspecting only several minutes? If so, that’s most likely the problem.
If you need faster registration system updates, follow up with me.
Honestly, I only saw it once in testing, it resolved some minutes after I saw it. None-the-less the one node that had reported having port forwarding in place was still unreachable - mostly. I confess I didn’t test access from one of my known good nodes, to the node that should be reachable.
Let me get back to them and validate that firewalls are properly configured etc before I spend any more of you guys time …
Thanks folks for the support - issue resolved - there was another device in the network chain that was not passing traffic - once it was set to “pass through” all was well.
Regularly there are folks that try and blame the issue they are having with ASL registration servers.
Most of the time it is NOT a problem with the registration servers as they have been very reliable and stable, but rather a error in configuration or networking by the user.
But we are always here to help whenever you need it!
73
Marshall - ke6pcv
···
From: Gerry Filby via AllStarLink Discussion Groups [mailto:noreply@community.allstarlink.org] Sent: Friday, June 19, 2020 7:56 PM To:ke6pcv@cal-net.org Subject: [AllStarLink Discussion Groups] 2 nodes having problems connecting to each other
Thanks folks for the support - issue resolved - there was another device in the network chain that was not passing traffic - once it was set to “pass through” all was well.
Honestly, I only saw it once in testing, it resolved some minutes after I saw it. None-the-less the one node that had reported having port forwarding in place was still unreachable - mostly. I confess I didn’t test access from one of my known good nodes, to the node that should be reachable.
Let me get back to them and validate that firewalls are properly configured etc before I spend any more of you guys time …
These nodes are registering with the ASL servers, not HamVoIP.
How much time had elapsed from the point node 51865 was brought on-line to the point where the
“rpt lookup 51865” was run from node 51879? I’m suspecting only several minutes? If so, that’s most likely the problem.
If you need faster registration system updates, follow up with me.
No worries, I was not trying to insinuate that you were blaming the registration servers.
I was just throwing that out there for information to all.
For the last few years, there has been a concerted effort going on by other folks to make ASL users think there is an issue with the registration servers.
This is clearly false information and I wanted to try and educate everyone of the truth.
73
Marshall - ke6pcv
···
From: Gerry Filby via AllStarLink Discussion Groups [mailto:noreply@community.allstarlink.org] Sent: Saturday, June 20, 2020 12:14 PM To:ke6pcv@cal-net.org Subject: [AllStarLink Discussion Groups] 2 nodes having problems connecting to each other
Regularly there are folks that try and blame the issue they are having with ASL registration servers.
Most of the time it is NOT a problem with the registration servers as they have been very reliable and stable, but rather a error in configuration or networking by the user.
But we are always here to help whenever you need it!
Thanks folks for the support - issue resolved - there was another device in the network chain that was not passing traffic - once it was set to “pass through” all was well.
Honestly, I only saw it once in testing, it resolved some minutes after I saw it. None-the-less the one node that had reported having port forwarding in place was still unreachable - mostly. I confess I didn’t test access from one of my known good nodes, to the node that should be reachable.
Let me get back to them and validate that firewalls are properly configured etc before I spend any more of you guys time …
I find if you add the outgoing (public IP) address to the node stanza in rpt.conf with the :4569 port number
it helps the nodes connect better, this works for outside nodes connecting in as well