[aprssig] aprs2.net client naming
Pete Loveall AE5PL Lists
hamlists at ametx.com
Wed Feb 28 16:18:07 EST 2024
SSIDs only designate unique stations associated with the callsign. If the station is directly seen on AX.25 RF, it must use 0 through 15 (no SSID on APRS-IS equals a zero SSID). On APRS-IS, any alphanumeric SSID of one or 2 characters is accepted by all server software. These rules are only for verified (valid passcode) "usernames". For receive-only, you can use any alphanumeric 3-9 characters as receive-only connections cannot send packets to APRS-IS.
Further information can be found at https://www.aprs-is.net
73,
Pete Loveall AE5PL
pete at ae5pl dot net
-----Original Message-----
From: aprssig <aprssig-bounces at lists.tapr.org> On Behalf Of John Gorkos
Sent: Wednesday, February 28, 2024 1:30 PM
To: TAPR APRS Mailing List <aprssig at lists.tapr.org>
Subject: [aprssig] aprs2.net client naming
Is there any kind of standardized/recommended naming practice for clients connecting to aprs2.net via (i.e.) aprsc?
I see some common threads to "username":
<call>-GS for DStarMonitor
<call>-10 for BrandMeister
Is this just a case of "if it fits in the <src> field of an AX-25 message, it's good-to-go? Any suggestions for Doing the Right Thing here? Does it even matter? :)
For clarity, I'm referring to the list of clients in the Clients section of the aprsc interface found, for example, here: http://205.233.35.46:14501/
Thanks,
John - AB0OO
More information about the aprssig
mailing list