[arm-allstar] Still receiving "Un-authorized" messages on Echolink connection

[David McGough]

Hi Mike,

I'm not sure how to solve this issue at the chan_echolink end; not at 
least without some major software changes.

When an echolink station tries to connect, first the locally stored
echolink nodelist is queried. If the node isn't found, a database update
is requested--that's the: "chan_echolink.c: Cannot find DB entry" message.  
Within a fraction of a second, chan_echolink typically receives an update
from the echolink database servers. If the echolink node number still 
can't be found, the connect request is just ignored--the packet is
dropped. It's then up to the connecting client to continue requesting to 
connect. Each time an attempt is made, chan_echolink will request a 
database update if the node info can't be found.

Here is an example I tried just now, using the Android echolink client, 
connecting through a relay.  Notice that a database update was requested 
and promptly received and I connected in about 1 second:


[Nov  3 23:26:39] NOTICE[480]: chan_echolink.c:2394 do_new_call: Cannot find DB entry for Callsign: KB4FXC, IP: . Requesting DB update.
    -- Received OK from Echolink server server2.echolink.org
    -- Directory pgm done downloading(partial,compressed), 323 records
    -- Received OK from Echolink server server2.echolink.org
    -- Received OK from Echolink server server2.echolink.org
    -- Directory pgm done downloading(partial,compressed), 497 records
    -- new CALL=KB4FXC,ip=44.190.9.222,name=        David KB4FXC
    -- Executing [1261 at radio-secure:1] NoOp("echolink/el0-5", "Date: 11/03/2019-23:26:40") in new stack
    -- Executing [1261 at radio-secure:2] Rpt("echolink/el0-5", "1212|X") in new stack
  == Spawn extension (radio-secure, 1212, 2) exited KEEPALIVE on 'echolink/el0-5'


If you're getting the database update after the request (indicated by the
"Directory pgm done downloading, xxx records" messages) and the connecting
node isn't in the echolink database, I'm wondering if the echolink
database servers are getting overwhelmed periodically?

BTW, I've tried this test (like above) several times tonight and don't 
see any problems. The client connects proptly.


73, David KB4FXC




On Sun, 3 Nov 2019, "Mike Sullivan via ARM-allstar" wrote:

> So, I have three separate nodes setup that I take care of currently, all
> running latest software and all Pi 3B's. Node 1 is on cable internet at the
> tower, node 2 is on cellular (AT&T) through a VPN, and node 3 is on
> cellular (Verizon) through a separate VPN. When connecting to all three
> nodes on Echolink from phone or computer, half the time I have no problem.
> But the other half of the time, I still receive at least 1-3
> "Un-authorized" messages before being able to connect. There's no set
> pattern at all on how often it happens.
> 
> Allstar log shows the following line, and it comes up multiple times on the
> unsuccessful attempts to connect:
> 
> [Nov  3 19:59:19] NOTICE[338] chan_echolink.c: Cannot find DB entry
> for Callsign: KN4IMU, IP: @. Requesting DB update
> 
> I've had several members from both of the clubs (Nodes 1 and 2) say they
> get this message often, and though they know why it's causing it and know
> to keep trying, I feel like new users trying to connect are discouraged
> from trying when they see the first "Un-authorized" message. There has to
> be some sort of fix for this.. I know it's not the connections because I
> have no other problems connecting out through Echolink, or in & out through
> Allstar on any of the nodes.
> 
> For those interested in testing, the nodes in question on Echolink are
> KN4IMU-L (personal simplex mobile), KG4DVE-R, and N8QA-R. If you get the
> error, let me know the time and I will try to pull log. I do have verbosity
> on KG4DVE-R turned up, I believe.
> 
> Mike
> _______________________________________________
> 
> 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
>