Possible bug found in the Echolink stuff?

App_rpt-users
1

Hi all,

I could find nothing about this in the archive so I thought I’d raise it here.

When using the Echolink app for Android (not tried on other platforms) and with the “Network Connection” set to “relay” when I try to connect to my node it gets hammered with connection requests that ultimately fail.

If I set the “Network Connection” to “direct” or “Public Relay” everything is fine and things connect first time and all is good.

I know someone is going to say “that’s an Android issue” but I think that ASL should handle this a little more gracefully.

Thanks

Mark/NI2O

2

I’ve now discovered that the issue is present with the Android app, Apple app and also the Apple RepeaterPhone app too.

When set to “relay” the apps hammer the receiving node with connection requests.

“direct”, Public Relay" or “custom Relay” seem to work just fine.

3

I would rather think you need to be talking to the Echolink folks and the independent folks that run relay servers. Issues have been present for more than a decade I believe.

4

If you have discovered a bug, please file a report at https://github.com/AllStarLink/app_rpt/issues. It will be helpful to have the information that you are viewing that shows the problem.

5

Oh, so this is known? Grrrrrr.

6

No, it is not a known issue w/ASL3.

What @Mike suggested was to check with the Echolink folks and the independent folks that run relay servers to see if this is something they are aware of.

What @kb4mdd asked was that you file an ASL3 bug report with as many details as you can. That information will help us investigate any possible issues with the ASL3 code base.

1 Like