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

[Tim Sawyer]

Hi All,

I'd like to get in on this conversation and I hope I don't get moderated. I
really don't want to start a flame war. I honestly want to know why using
the client provided port is bad. I'll take those reasons back to the
Allstarlink team for their consideration. We're trying to make AllStar
better and if we made a mistake we want to correct it.

On Sun, Aug 12, 2018 at 9:16 PM "Danny K5CG via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> "The port will be picked up from the bindport address and passed as part
> of the registration"
>
> Sounds like a good solution Doug.
>
> The only thing I would ask as a "nice to have" is the ability to specify
> an override of the registration port. I might have UDP 4569 open on my node
> but want my firewall to expose 14569 and translate it to 4569 inward. I
> could live without it, just change the node to 14569, but it adds
> flexibility.
>
> Danny
> K5CG
>
> ----- Original Message -----
> From: "ARM Allstar" <arm-allstar at hamvoip.org>
> To: "ARM Allstar" <arm-allstar at hamvoip.org>
> Cc: "wa3dsp" <wa3dsp at gmail.com>
> Sent: Sunday, August 12, 2018 10:52:49 PM
> Subject: Re: [arm-allstar] Notice of Allstar problems and how to diagnose
>
> Yes, This is exactly the case and they are too hard headed to realize it.
> They think it is the users responsibility to fix it, NOT!
>
> The hamvoip registration system will not be using Asterisk and is written
> from the ground up to specifically handle Allstar registrations. It is
> robust and has been tested to ten times the current load. The port will be
> picked up from the bindport address and passed as part of the registration
> process thus freeing the user from having to do anything beyond setting the
> bindport in iax.conf.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
>
> On Sun, Aug 12, 2018 at 11:18 PM, "Danny K5CG via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > "The problem is that some routers in fact many (it is about 700 in the
> > current list) do not report proper ports"
> >
> > And it isn't a "problem" with the routers, or proper ports, per sé. The
> > problem is that ASL is now relying on the false assumption that the
> "proper
> > port" is the one from the source. BAD DOG!
> >
> > I'm frankly surprised there aren't more nodes affected.
> >
> > My node is one of the affected, but I'm not making any changes to my
> > router. I'll wait for a proper solution which is universal and robust.
> >
> > Danny
> > K5CG
> > _______________________________________________
> >
> > 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



-- 
Tim WD6AWP