[arm-allstar] Notice of Allstar problems and how to diagnose

[John Wagner]

Thanks for the command Doug.

Yep, +1 here. That's what's causing the problem with our nodes that just
started a few days ago.

[root at 5317-42993 ~]# check_reg.sh

Node - 42993 at IP address 24.166.41.151:9528 is Auth.
 DNS lookup returns - +OK|radio at 24.166.41.151:9528/42993,24.166.41.151

The :9528 should be :4588 for that node. I have 7 nodes behind a fairly
modern Juniper SRX300 router that (properly) randomizes source ports
through it's NAT function. I verified on the router that it is in fact
randomizing the source port to 9528 on the way out. It's been doing that a
long time and working fine till last week. I didn't check the others on our
network but I'm sure they will have the same issue.

I believe I can put some lines in the SRX router config to tell it not to
randomize source ports for certain hosts, so I'll probably begrudgingly do
that in the interim.

FWIW, our ham-metro network also has a site with a Hytera DMR repeater on
Brandmeister going out the same router and NAT, and they also do the same
irritating thing with expecting a fixed source port. I had to exempt that
too in the same way. That system is a whole other aggravating networking
travesty. Grrrrr.

 - John, N8CD


On Sun, Aug 12, 2018 at 11:53 PM, <arm-allstar-request at hamvoip.org> wrote:

>
>
> ------------------------------
>
> Message: 5
> Date: Sun, 12 Aug 2018 22:49:33 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: [arm-allstar] Notice of Allstar problems and how to diagnose
> Message-ID:
>         <CAMp6vsu+gieprGSaVbzK=3-2EcT=YsNnf2hv7emQz4mFMcDk2w at mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> As I pointed out earlier the Allstar group has created a mess with their
> supposed new and improved (and previously untested) registration system.
> The problem is that some routers in fact many (it is about 700 in the
> current list) do not report proper ports. Since the new Allstar
> registration SW does not use the Allstarlink.org supplied port and your
> router does not either then you are out of luck under the current system.
> If you are having problems do the following.
>
> First see if you are registered.
>
>       check_reg.sh    or     asterisk -rx "iax2 show registry"
>
> You will see something like this -
>
> DNS lookup returns - +OK|radio at 67.165.29.63:4569/40561,67.165.29.63
>
> Look at the IP address after the @ and ensure it is correct for your public
> IP address. Then and more importantly check the IAX port - the number after
> the ":"   It is shown as this example as 4569
>
> If you use the iax2 show registry method it will be under the perceived
> column.
>
> If this number does not match the IAX port you have set in your
> /etc/asterisk/iax.conf file on the bindport=  line then you will not be
> able to use your node. Changing the bindport setting will NOT fix the
> problem as the perceived port at the Allstar end is random.
>
> If your system is one currently experiencing this problem there is nothing
> you can do at your end to fix it besides maybe getting a new router which
> we do not recommend. The Allsar end has to fix the problem which we are
> hoping they will do. If not just watch here for an update due to come out
> very soon to fix the problem.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
>