[arm-allstar] Echolink "Un-authorized" connection messages

Fri Aug 23 01:53:30 EDT 2019

Try not using a proxy. Use you cell Internet, turn off wifi.

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Fri, Aug 23, 2019 at 12:07 AM "Mike Sullivan via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> That’s the point I was trying to make. The rate it happens is so inaccurate
> that I don’t know if it’s an error on Echolink’s part, on the database
> server, on the polling between Hamvoip and the Echolink database, or what.
> Sometimes I can immediately log in and have no problem at all connecting,
> even after not logging in to Echolink for days. Other times, I can’t log in
> even after waiting X seconds, and as the logs show, either it fails to get
> the database and it checks the last received database, or my node doesn’t
> appear for whatever reason.
>
> That’s why I was also asking what rtcptimeout is for. Maybe it just needs
> more time to receive a database update from the server before rejecting the
> connection. I feel like anyone that is trying to connect to Echolink & sees
> that they’re unauthorized and thinks they aren’t welcome.
>
> Mike
>
> On Thu, Aug 22, 2019 at 23:32 "Doug Crompton via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > There was nothing changed in updates for quite awhile in echolink so I
> > doubt that has anything to do with it. When your echolink node comes
> online
> > it will take a period of time for it to appear in the database. Echolink
> > has had its share of connection problems on and off. Allstar attempts to
> > update the database on connection several times. If it is not there after
> > that it fails but that does not mean you cannot try again a minute or two
> > later. This may also have something to do with proxy connections which
> may
> > not always show up in our database.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Thu, Aug 22, 2019 at 11:27 PM "Steve Polley via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Doug,
> > >
> > > I have ran into the problem occasionally also running the latest
> update.
> > >
> > > Steve
> > > N0SWP
> > >
> > > On Thu, Aug 22, 2019 at 9:54 PM "Doug Crompton via ARM-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > Mike,
> > > >
> > > >  Dave could give more details on this but from what you say if you
> are
> > > > getting the database then you should be registered with Echolink. It
> > > sounds
> > > > like that message would be issued if you were not registered. Are you
> > in
> > > > the database that gets downloaded? Echolink has three possible
> > variations
> > > > for your call - W3XYZ, W3XYZ-L, and W3XYZ-R. Each can have a
> different
> > > > password or they all can be the same only one can be used per
> distinct
> > > > public IP address. At this time no one else has reported this issue
> so
> > it
> > > > seems it might be connected to something going on within your system.
> > > >
> > > >
> > > > *73 Doug*
> > > >
> > > > *WA3DSP*
> > > >
> > > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
> >*
> > > >
> > > > On Thu, Aug 22, 2019 at 8:50 PM "Mike Sullivan via ARM-allstar" <
> > > > arm-allstar at hamvoip.org> wrote:
> > > >
> > > > >  Back when I was first setting up our club's Allstar node, I was
> > > > reporting
> > > > > on an issue where Echolink would report that I was un-authorized to
> > > > connect
> > > > > to the node, but subsequent attempts, I was able to connect fine. I
> > > > figured
> > > > > this was just a fluke with our node, but I set up a second node at
> > > > another
> > > > > club's tower, which runs through an OpenVPN tunnel instead of a
> > direct
> > > > > cable connection. Both nodes have the same problem, just not
> > > constantly.
> > > > > Most times I have no problem, but there will be the occasional time
> > > that
> > > > it
> > > > > fails to connect and says I'm un-authorized.
> > > > >
> > > > > In checking the Allstar log on either node after this happens, I
> see
> > > > > multiple subsequent requests for a database update when it does
> fail.
> > > The
> > > > > failed attempts are separated 2 seconds apart, and can be anywhere
> > from
> > > > 4-8
> > > > > times I have seen, but always result in a failed connection. Other
> > > times
> > > > it
> > > > > is just a single DB update and no problem connecting. Running
> > 'echolink
> > > > > dbdump' in CLI produces a valid database.
> > > > >
> > > > > Could this be an issue on Echolink's database end, or is there
> > > something
> > > > I
> > > > > can do with Allstar to ensure the node updates more regularly? I
> > can't
> > > > find
> > > > > any other evidence listed. I've attached copies of the logs below.
> > > > >
> > > > > Mike
> > > > >
> > > > > Failed attempt
> > > > >
> > > > > [Aug 22 19:45:16] NOTICE[27272] chan_echolink.c: Cannot find DB
> entry
> > > > > for Callsign: KN4IMU, IP: H��v103.85.188. Requesting DB update.
> > > > > [Aug 22 19:45:18] NOTICE[27272] chan_echolink.c: Cannot find DB
> entry
> > > > > for Callsign: KN4IMU, IP:  ��v103.85.188. Requesting DB update.
> > > > > [Aug 22 19:45:20] NOTICE[27272] chan_echolink.c: Cannot find DB
> entry
> > > > > for Callsign: KN4IMU, IP: p��v103.85.188. Requesting DB update.
> > > > > [Aug 22 19:45:22] NOTICE[27272] chan_echolink.c: Cannot find DB
> entry
> > > > > for Callsign: KN4IMU, IP: н�v103.85.188. Requesting DB update.
> > > > > Successful attempt
> > > > >
> > > > > [Aug 22 19:55:08] NOTICE[27272] chan_echolink.c: Cannot find DB
> entry
> > > > > for Callsign: KN4IMU, IP: 0��v103.85.188. Requesting DB update.
> > > > > _______________________________________________
> > > > >
> > > > > 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
> > _______________________________________________
> >
> > 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