[arm-allstar] If a node connects to another node, and the 2nd node later disconnects, is the 1st node or ASL notified?

[David McGough]

David,

The updated HamVoIP firmware is already very widely distributed.  Only a 
few percent of nodes are still running the problematic original release 
from 12/2021.  It just happens that node 404122 is one of the few 
that haven't been updated.

Tell the node 404122 owner the update is painless.  Just run option #1
from the admin menu and a minute later it's done.  Problem resolved.

73, David K4FXC


On Mon, 4 Jul 2022, "David Gleason via ARM-allstar" wrote:

> Hi David,
> 
> Thanks for the quick reply and for solving this mystery. That would 
> explain why ASL stats would not get updated.
> 
> BTW I did also open a ticket with ASL and asked (in the meantime until 
> the newer FW is widely deployed) if they might be able to do a 
> fix/enhancement to the stats to cross reference the connection data and 
> only show connections on their website if both nodes report the 
> connection. Otherwise in this case people were concluding that one node 
> was 'hacking' the other node and connecting to it without the other 
> node's knowledge, which seems highly unlikely because a node is probably 
> not going to forward VOIP packets anywhere if it doesn't know a 
> connection is open.
> 
> Thanks,
> David
> NR9V
> 
> On 7/4/2022 7:24 AM, David McGough via ARM-allstar wrote:
> > David,
> >
> > I just looked at the ASL stats pages. Node 404122 needs to be updated,
> > it's running the original HamVoIP 1.7 release, which had the stats bug.
> >
> > http://stats.allstarlink.org/stats/404122
> >
> >
> > 73, David K4FXC
> >
> >
> > On Mon, 4 Jul 2022, "David McGough via ARM-allstar" wrote:
> >
> >> Make sure your node is fully updated using option #1 from the admin menu,
> >> this issue was corrected in the hamvoip-V1.7.0-03 release in Jan, 2022.
> >>
> >>
> >> 73, David K4FXC
> >>
> >>
> >> On Sun, 3 Jul 2022, "David Gleason via ARM-allstar" wrote:
> >>
> >>> I notice that if someone connects to my ASL node and I later disconnect
> >>> them from my node, that the ASL stats pages (at least in some cases)
> >>> then continue to show that the other node is still connected to my node
> >>> even though it is definitely not (eg. my node might then be powered off
> >>> for hours yet is still shown in other nodes' ASL stats pages and bubble
> >>> charts). In terms of the IAX protocol packets exchanged between the
> >>> nodes, when a node disconnects an inbound connection is the originating
> >>> node notified? And is a stats update sent to ASL?  If so, why would the
> >>> ASL stats pages continue to show a node as being connected when in fact
> >>> it is not connected (and may have been powered off for hours or days).
> >>> Any tips on these connect/disconnect protocol details would be much
> >>> appreciated. Seems it would be helpful to nodes that originated a
> >>> connection and to the ASL stats system to know when a destination node
> >>> closed a connection so their stats would then be correct and up-to-date.
> >>>
> >>> Thanks,
> >>> David
> >>> _______________________________________________
> >> 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