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.

Here’s what I gathered from the asterisk CLI

node51865CLI> rpt lookup 51879
Node: 51865, Method: DNS, Actual: DNS, Data: radio@135.180.5.78:4569/51879,135.180.5.78
Node: 1999, Method: DNS, Actual: DNS, Data: radio@135.180.5.78:4569/51879,135.180.5.78
node51865
CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
216.244.83.154:4569 Y 51865 107.210.159.55:4569 60 Registered

node51879CLI> rpt lookup 51865
Node: 51879, Method: DNS, Actual: LOCAL, Data: NOT FOUND
Node: 1999, Method: DNS, Actual: DNS, Data: radio@107.210.159.55:4569/51865,107.210.159.55
node51879
CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
178.32.160.82:4569 Y 51879 135.180.5.78:4569 60 Registered

It’s the “NOT FOUND” that stands out to me - try again later and it will resolve itself.

Is it possible one of the registrations is unhappy on one of the registration servers ?

g

Gerry,

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





|

W6WNG
June 18

|

  • | - |

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.

Here’s what I gathered from the asterisk CLI

node51865CLI> rpt lookup 51879
Node: 51865, Method: DNS, Actual: DNS, Data: radio@135.180.5.78:4569/51879,135.180.5.78
Node: 1999, Method: DNS, Actual: DNS, Data: radio@135.180.5.78:4569/51879,135.180.5.78
_node51865_CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
216.244.83.154:4569 Y 51865 107.210.159.55:4569 60 Registered

node51879CLI> rpt lookup 51865
Node: 51879, Method: DNS, Actual: LOCAL, Data: NOT FOUND
Node: 1999, Method: DNS, Actual: DNS, Data: radio@107.210.159.55:4569/51865,107.210.159.55
_node51879_CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
178.32.160.82:4569 Y 51879 135.180.5.78:4569 60 Registered

It’s the “NOT FOUND” that stands out to me - try again later and it will resolve itself.

Is it possible one of the registrations is unhappy on one of the registration servers ?

g


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

Gerry,

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.

73, David KB4FXC

They’ve both been online for a couple of days, certainly more than a couple of hours at the point I was testing.

Thanks guys …

How long did the “NOT FOUND” issue persist for?

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.

Best,
Gerry.
W6WNG

Gerry,

Glad that you found what was causing the problem.

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





|

W6WNG
June 20

|

  • | - |

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.

Best,
Gerry.
W6WNG


Visit Topic or reply to this email to respond.


Previous Replies





|

W6WNG
June 19

|

  • | - |

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 …





|

David_McGough
June 19

|

  • | - |

How long did the “NOT FOUND” issue persist for?





|

W6WNG
June 19

|

  • | - |

They’ve both been online for a couple of days, certainly more than a couple of hours at the point I was testing.

Thanks guys …





|

David_McGough
June 19

|

  • | - |

Gerry,

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.

73, David KB4FXC





|

KE6PCV ASL Admin
June 19

|

  • | - |

Gerry,

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

··· (click for more details)


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

No blame intended whatsoever. Just trying to figure out how to get the node to a functional state …

Thanks again,
Gerry
W6WNG

Gerry,

No worries, I was not trying to insinuate that you were blaming the registration servers. :slight_smile:

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





|

W6WNG
June 20

|

  • | - |

No blame intended whatsoever. Just trying to figure out how to get the node to a functional state …

Thanks again,
Gerry
W6WNG


Visit Topic or reply to this email to respond.


Previous Replies





|

KE6PCV ASL Admin
June 20

|

  • | - |

Gerry,

Glad that you found what was causing the problem.

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

··· (click for more details)





|

W6WNG
June 20

|

  • | - |

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.

Best,
Gerry.
W6WNG





|

W6WNG
June 19

|

  • | - |

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 …





|

David_McGough
June 19

|

  • | - |

How long did the “NOT FOUND” issue persist for?





|

W6WNG
June 19

|

  • | - |

They’ve both been online for a couple of days, certainly more than a couple of hours at the point I was testing.

Thanks guys …


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

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

42668 = radio@192.168.0.30:4568/42668,NONE
42353 = radio@56.55.42.39:4569/42353,NONE

as example