[arm-allstar] telemetry control

[Larry]

David,

My Feeling you do enough already ...why waste your time on something 
like that. You've got it right already.

I don't see why it matters what "neighboring nodes" do. That is like 
asking to broadcast who is monitoring RF links on a system. We sure 
don't need to broadcast all that garbage even if we knew who was lurking 
about. If a station wants to talk fine identify yourself and talk. 
Otherwise who cares who comes and goes.

If he means he wants his own system to broadcast connects/disconnects 
from his own nodes out his HUB ... build a script to monitor all the 
coming and going from the different LOG files on his own network and 
announce it some where locally but certainly not to the entire network 
if his node is connected outbound.

Larry - N7FM


On 1/27/22 2:37 PM, "David McGough via ARM-allstar" wrote:
> Okay, I'm going to have to investigate a solution.  The issue is that
> telemetry from the "neighbor node" indicating the connection change
> probably isn't being passed to your hub, no matter how telemenabled is set
> at your end. So, you don't know a node has connected to a neighbor, other
> than by monitoring linkslist data, as seen in Supermon, etc. Note that the
> linkslist data is updated.