[arm-allstar] Permanent link failing

David McGough kb4fxc at inttek.net
Wed Jun 21 14:47:10 EST 2017 

Hi Chris,

Well, the networking between the nodes should be very stable, based on 
your description. I've got some on those HP switches, too, and they're 
rock solid.

One thing worth checking would be the kernel messages ("dmesg" command) on 
both nodes, once the problem shows up. Otherwise, I'm not sure what could 
be going on, I've not seen this happen on my systems, so far.

Just as a (probably completely unrelated) footnote, typically when I've
had strange one-way audio issues, the problem was that Asterisk couldn't
negotiate the CODEC to use properly.....I am reminded of this since I
added CODEC2/3200 back to our alpha codebase recently and forgot to
disable it on my test repeater (oops).

73, David KB4FXC


On Wed, 21 Jun 2017, C B wrote:

> Thanks for replying
> For nodes to talk to each other do not go they the firewall as they are on the same sub net and have the correct route information in the rpt.conf file.
> the firewall is NAT type model TLR600-VPN by TP-link, however the nodes to not use the firewall or the internet to talk to each other.
> This is on  VLAN with HP Procurve 2900 series switches.
> this does not happen on the internet connected nodes that are using the firewall, however there is only one that connects via the internet with a permanent link however so that could be just luck that it has not happened.
> Thanks again for your help.
> Chris
> 
>       From: David McGough <kb4fxc at inttek.net>
>  To: C B via arm-allstar <arm-allstar at hamvoip.org> 
> Cc: C B <harvard5362 at yahoo.com>
>  Sent: Wednesday, June 21, 2017 9:53 AM
>  Subject: Re: [arm-allstar] Permanent link failing
>    
> 
> Chris,
> 
> Are these nodes going through NAT or a connection-tracking firewall?
> 
> 73, David KB4FXC
> 
> 
> 
> On Wed, 21 Jun 2017, "C B via arm-allstar" wrote:
> 
> > Another piece of information
> sometimes the failure passes audio and key-up information in one direction and not the other, other times it fails in both directions.
> 
>       From: C B <harvard5362 at yahoo.com>
>  To: ARM Allstar <arm-allstar at hamvoip.org> 
> Cc: Doug Crompton <wa3dsp at gmail.com>
>  Sent: Wednesday, June 21, 2017 9:29 AM
>  Subject: Re: [arm-allstar] Permanent link failing
>   
> Thanks for the quick response.
> All nodes involved here are my nodes.
> All are your code on PI-3's with the latest updates.
> Very stable on my microwave.
> Not relying on the /tmp/rpt_extnodes file  as all are hard coded in the rpt.conf file with the ip address and port number as my nodes are all on the same private sub-net. Below is a example of what is in the rpt.conf file i only pasted the first 3 lines. i commented out 1999 as it is not used. Information for all of my nodes are in the rpt.conf as they all have a differnt port and are behing the same firewall.
> 43816 = radio at 127.0.0.1/43816,NONE;1999 = radio at 127.0.0.1/1999,NONE27008 = radio at 10.0.1.22:4568/27008,NONE
> The nodes think they are connected as allmon2 reports them as connected and if i am not mistaken allmon2 gets its connection information from each node.
> this issue is very intermittent and not easily repeated. It occurs anywhere from a few days to a few months, and as it does not show up as an issue on allmon2 it is hard to know when it has occurred.
> Thank you again for your help.
> 
> 
> 
>       From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
>  To: ARM Allstar <arm-allstar at hamvoip.org> 
> Cc: Doug Crompton <wa3dsp at gmail.com>
>  Sent: Wednesday, June 21, 2017 9:05 AM
>  Subject: Re: [arm-allstar] Permanent link failing
>   
> Chris,
> 
>   I have not seen this problem here and I run several permanent
> connections. Keep in mind that whoever you are connecting to can manually
> disconnect a permanent link to them. So if the node you are connecting to
> is not yours or it is yours and you are not sure if someone could be
> disconnecting from the other end check to see if that might be the case.
> 
> To better understand why this might be happening we would need more info.
> Are the links generally reliable or are they constantly
> disconnecting/reconnecting? What code version is a BOTH end? Is there any
> situation that you can identify when this happens? You can go into the
> Asterisk client (ADMIN menu item 11) and view the log to see if reconnects
> are taking place.
> 
> Asterisk requires that both ends have knowledge of the other ends IP
> address. This is done through the /tmp/rpt_extnodes file. If one end (your
> end) had the connection list and the other end did not the connection would
> fail and your end would continue to try and reconnect forever until either
> you restarted/rebooted or you execute a permanent disconnect. During this
> period if you had previously been connected the connection list would
> probably still show connected.
> 
> 
> *73 Doug*
> 
> *WA3DSP*
> 
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> 
> 
> 
> 
> 
> On Wed, Jun 21, 2017 at 11:23 AM, "C B via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
> 
> >
> >
> >
> > Randomly my Permanent links are acting as if they are notconnected. Almon2
> > still shows them as connected however the signals to not passthru.
> >
> >
> > Background on my configuration.
> >
> >
> > There are more than 30 nodes in the system that is connectedon the same
> > private sub net, on a vlan on the wide area intranet; this intranetconsists
> > mostly of IP microwave.  All nodessit behind a router. There are also nodes
> > connected via the public internet.
> >
> >
> > Each node has a unique port number, there is a line in eachnode in the
> > prt.conf so that the private ip address and port are known for eachof the
> > nosed on the same subnet of the wide area intranet. Thus this is notrelying
> > on a hairpin thru the router for connectivity.
> >
> >
> > The nodes Permanent link is set up by having a startup_macro=*73xxxxxxxxin
> > the rpt.conf
> >
> >
> > Every so often a node no longer is linked but it still showslinked in
> > allmon2.
> >
> >
> > Restarting asterisk resolved this issue.
> >
> >
> > Any idea on what can be done here to make this more reliable?
> >
> >
> > Thank you in advance for any help.
> >
> >
> > Chris
> >
> > _______________________________________________
> >
> > 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 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 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 web page - http://hamvoip.org
> 
> 
> 
>

More information about the arm-allstar mailing list