[arm-allstar] Link Activity Timer Not Always Working
Larry Aycock
N6LKA at outlook.com
Thu Oct 22 19:18:18 EDT 2020
Hi David,
No, this problem has been occurring for a while now but has been happening more frequently within the last week or so. Before, it would only do it on my dad's node very rarely. Now, my friend's repeater is also doing it, and the frequency of the two disconnecting and not reconnecting has significantly increased. I moved the hub node to a cloud server this morning for various reasons, one of which was to eliminate the possibility that it might be something wrong with my repeater node. However, after setting up the cloud hub, one of the other nodes has already disconnected and didn't reconnect, indicating the problem still exists and wasn't an issue with my repeater node.
I had to use ASL for the cloud node since I don't think I can install HamVoip on a virtual server. However, the other three nodes (my repeater, friend's repeater, and my dad's node) are all running the latest version of HamVOIP. I'm not sure what dual-registration is, so I can't answer that question.
73,
Larry Aycock
N6LKA
-----Original Message-----
From: David McGough <kb4fxc at inttek.net>
Sent: Thursday, October 22, 2020 3:44 PM
To: Larry Aycock via ARM-allstar <arm-allstar at hamvoip.org>
Cc: Larry Aycock <N6LKA at outlook.com>
Subject: Re: [arm-allstar] Link Activity Timer Not Always Working
Larry,
Did this problem start after changing to using a VPS-based hub node?
Are you using HamVoIP dual-registration?
73, David KB4FXC
On Thu, 22 Oct 2020, "Larry Aycock via ARM-allstar" wrote:
> Hello,
>
> For a while now, I have been using the link activity timers on a few
nodes/repeaters, and they have been working for the most part. I have a hub node, which I just moved to a cloud server. I have my repeater node, a friend's repeater node, and my dad's simplex node connecting to my hub node. On my repeater, my friend's repeater, and my dad's node, we use the link activity timer to disconnect all nodes and reconnect back to my hub node. As I mentioned, this has been working for the most part.
However, on my friend's repeater and my dad's node, it will occasionally disconnect from the hub, and won't reconnect. Hours will pass and it will not reconnect back to the hub. Eventually, one of us will notice the link is down, and send the command to run the script, and it reconnects back to the hub. Nothing has changed on either of the nodes, and it seems like this problem is occurring much more frequently within the past week.
>
> Note that my repeater has not had this problem with disconnecting and
remaining disconnected. However, the hub node was, prior to this morning, hosted on the same RPi as my repeater node. I moved the hub node to a cloud server for several reasons, but was also trying to troubleshoot this problem. Unfortunately, even once I moved the hub to the cloud, I found the problem with the two nodes remaining disconnected is still happening. I am baffled by this problem because it doesn't always happen. I have not been able to consistently recreate the problem, so I have not been able to identify the cause.
>
> Below is a copy of the part from my rpt.conf file used on my repeater.
Remember that I am not having this problem with my repeater, but the same lines are used in my dad's and my friend's rpt.conf files.
>
<snip>
>
>
> 73, Larry, N6LKA
>
>
More information about the ARM-allstar
mailing list