开云体育

Regarding this station that is flooding the world with TACTICAL message:

I've done some looking at this station, and he is rather abusive of the network. He has a digipeater PT2VHF-1 sending its beacon every minute (not that the digipeater is moving anywhere), so when is anyone else going to get a moment to get a packet in to be digipeated? :-( His digipeater is apparently also an I-gate, because it is feeding the beacons directly to APRS-IS, using a tocall of APE32I. Anybody recognize that software/firmware type?

He also has (apparently) a copy of SARtrack running at his home PT2VHF-3 transmitting both its beacon and the TACTICAL message every 15 seconds (!), no position change. Since he is directly connected to the APRS-IS backbone, the T2BRAZIL backbone server isn't throttling his excessive transmission rate the way a digipeater would. I wonder if he is transmitting the same rate on RF; we would never see it since he is sending direct to APRS-IS so no other I-gate could possibly get it in faster than he does.

Of course, we don't know if any of this is actually about that station; it could be a fraudulent false identity trying to jam the APRS-IS. Any Brazilian operators on these mailing lists who know this operator?

Since he is not sending anything useful, I would recommend using YAAC's blacklist feature to block his callsign-SSIDs (disabling at least QUERY operations for his callsign-SSID). Blacklisting is persisted, so you won't have to keep setting it up.

Jamie, hope this helps. I'm still going to make some of the other fixes I proposed to make this sort of thing less likely to happen by accident. Bart ZL4FOX, is there a mode in SARTrack that could let a user do this sort of network abuse? And to the keepers of the APRS-IS backbone, should Tx I-gates provide the same sort of duplicate throttling that New-N digipeaters do (no more than one identical packet in 30 seconds)? I want to check my code to ensure I'm throttling like that on a Tx I-gate configuration.

Andrew, KA2DDO
author of YAAC ("Yet Another APRS Client")

________________________________________
From: [email protected] <[email protected]> on behalf of Andrew P. <andrewemt@...>
Sent: Monday, October 21, 2024 8:23 AM
To: [email protected]
Subject: Re: [yaac-users] Tactical Messages from PT2VHF

Whenever the dialog announcing tactical messages from that user comes up, click the "Never" button. That will remember that decision as long as YAAC remains up.

Considering how annoying these messages can be, I'm thinking about making some changes to this:

1. Persist a "Never" or "Always" decision for a specific sending callsign over YAAC restarts. However, then there would have to be a way to delete the persisted settings if they were no longer wanted.
2. Ignore TACTICAL messages to get your local tactical aliases entirely if you don't have any defined, so the annoying dialog won't come up if you have nothing to send to the requestor.
3. Fix YAAC's sending of TACTICAL messages to be RFONLY,NOGATE so that it won't go to the APRS-IS unless someone specifically changes the configuration to enable it. Since TACTICAL names are supposed to be local (not global), those messages really shouldn't be going over the Internet. The menu choices to send and get tacticals isn't even enabled in YAAC unless you have an open RF port, but any station set up as an I-gate would presently allow the messages to be sent to APRS-IS as well as RF.

I need to check how many of those annoyances are coming from YAAC (as opposed to some other program like Xastir), and see if the present default behavior of YAAC is contributing to noise.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Jamie H <wa7jh@...>
Sent: Sunday, October 20, 2024 8:02 PM
To: [email protected]
Subject: [yaac-users] Tactical Messages from PT2VHF

I keep getting tactical messages from this call, can I turn that shit off?

Jamie Hughes
WA7JH
(360) 340-8886