Multiple logins to the same tier2 aprs server?

[C Lamparter]

I have a few aprsis clients, all of which use my callsign and login.  I'm noticing if two clients login to the same tier2 server, one gets logged off, or other odd behavior ensues.  I don't think using a different ssid helps.

For resiliency I'd like to use noam.aprs2.net round robin, but not if there's a good chance clients will land on the same server.

Is there an orthodoxed way to do this?  Are my observations founded?

thanks!
-craig

[Lynn W Deffenbaugh (Mr)]

Yes, your observations are founded.  That is the way the servers behave to keep their connections clean.  Every client in concurrent operation must use a unique callsign-SSID.  Just add unique -SSIDs to your various clients and your multi-login difficulties will quit happening.  From http://www.aprs-is.net/Connecting.aspx (emphasis their's):

• mycall-ss=your unique callsign-SSID (-SSID is optional but equates to zero if omitted, see below). This must be unique throughout APRS and AX.25.
  

Note that for the APRS-IS login, the -SSID does NOT have to be AX.25 compliant.  Just check the following URL for a sample of non-standard -SSIDs.

https://aprs.fi/#!call=KJ4ERJ-*

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

--
You received this message because you are subscribed to the Google Groups "aprs.fi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprsfi+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/aprsfi/c5f5a566-63e1-48a8-9a1e-149699674bdc%40googlegroups.com.

[Heikki Hannikainen]

Please note that the APRS-IS servers will also drop packets which are
gated by a callsign-SSID which matches a locally-connected client, if the
packet comes in via any other socket than that particular local client.
Even if you successfully land the duplicate-callsign-SSID clients on
different servers, there will be packet loss for you. The callsign-SSID
pair must be unique on the APRS-IS.

http://aprs-is.net/qalgorithm.aspx

"""
If a verified login other than this login is found in the q construct
AND that login is not allowed to have multiple verified connects
(the IPADDR of an outbound connection is considered a verified login):
{
Dump to the loop log with the sender's IP address for identification
Quit processing the packet
}
"""

PS. This question is not about aprs.fi, so please, if you have any further
questions about APRS-IS, please move to another forum, such as the
APRSSIG. Thanks!

On Fri, 12 Jul 2019, Lynn W Deffenbaugh (Mr) wrote:

> Yes, your observations are founded.  That is the way the servers behave to keep their connections clean.  Every
> client in concurrent operation must use a unique callsign-SSID.  Just add unique -SSIDs to your various clients and
> your multi-login difficulties will quit happening.  From http://www.aprs-is.net/Connecting.aspx (emphasis their's):
>

> o mycall-ss=your unique callsign-SSID (-SSID is optional but equates to zero if omitted, see below).

> https://groups.google.com/d/msgid/aprsfi/dcc0d3e5-45ab-3e5c-332d-ad6951877803%40gmail.com.
>
>

- Hessu