[arm-allstar] telemetry control

David McGough kb4fxc at inttek.net
Thu Jan 27 17:37:23 EST 2022


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.

I'll mention that I've explicitly changed HamVoIP to alter this behavior.  

The problem is that historically there have been telemetry "storms"
frequently occurring on larger networks, where a small number of nodes
will quickly connect and disconnect from some edge location, sending an
oscillating wave of telemetry messages across the entire network, with
crippling impact! This type problem is now resolved. Going backwards to
the previous mechanism verbatim isn't an option, so I'll try to find a
solution which allows the desired telemetry action, without to potential
network pitfalls.


73, David KB4FXC



On Thu, 27 Jan 2022, "Patrick Perdue via ARM-allstar" wrote:

> My personal observation is that telemetry is only passed on the local 
> node. Foreign links are ignored, even on ASL hubs which don't care about 
> this parameter. If I use
> 
> telemdefault=1
> 
> and
> 
> telemenabled=255
> 
> I get voice telemetry when someone connects directly to my node, but not 
> if someone connects to a linked node.
> 
> For example, if I connect to 508420 from 508423, I get telemetry on 
> 508420. However, if 508420 is connected to 506311, and I connect to 
> 506311 from 508423, I get nothing on 508420.
> 
> 
> On 1/27/2022 5:06 PM, "David McGough via ARM-allstar" wrote:
> > Chris,
> >
> > What's missing?  I am heavily re-writing all this code.
> >
> >
> > 73, David KB4FXC
> >
> >
> > On Thu, 27 Jan 2022, "Chris via ARM-allstar" wrote:
> >
> >> From: ARM-allstar <arm-allstar-bounces at hamvoip.org> On Behalf Of "David
> >> McGough via ARM-allstar"
> >>
> >>
> >> telemenabled=255 should get everything turned back on.
> >>
> >> It does not on my two nodes running the latest update.
> >> I have both of these in rpt.conf:
> >> telemenabled=255
> >> holdofftelem=0
> >>
> >> _______________________________________________
> >>
> >> ARM-allstar mailing list
> >> ARM-allstar at hamvoip.org
> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>
> >> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
> >>
> > _______________________________________________
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
> _______________________________________________
> 
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
> 



More information about the ARM-allstar mailing list