开云体育

开云体育

________________________________________
From: [email protected] <[email protected]> on behalf of Lynn Deffenbaugh <kj4erj@...>
Sent: Tuesday, October 22, 2024 2:15 PM
To: [email protected]
Subject: Re: [APRS] [yaac-users] Tactical Messages from PT2VHF

Thankfully you only need to learn a few things at a time, but you're correct, there's a LOT to APRS (and we haven't even mentioned direction-finding/fox-hunting support objects recent).

But two dots just connected in my brain, so circling back to the original question about filtering out Tactical messages, it should be possible to eliminate these coming from the APRS-IS with the following filter term:


-g/TACTICAL

The minus is a negative or "don't include these" as mentioned by Pete recently and the g/ is a "group message" filter removing all messages directed to TACTICAL.



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




On 10/22/2024 12:35 PM, Luzemario PR7LDR wrote:
On Tue, Oct 22, 2024 at 08:55 AM, Lynn Deffenbaugh wrote:
(SAR)#Tactical_Callsigns
Guys, thank you very much for your answers. It sounds like a trap for novices like me... ;-)

This reminds me of John WB2OSZ talking about various APRS extensions in his docs. Those like me who have never done packet radio or APRS before, have a steep learning curve.

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

开云体育

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

My guess is that you can filter messages.

Look under 'Contents' of the 'Help' menu then in the 'Table of
Contents': 'Menus' then click on 'Filter'.

As a new user just started, I can't be more specific until I finish
working my way through the Help system.

Andrew, W5AWS.
-=-=-=-

开云体育

next beta build#204 of YAAC ("Yet Another APRS Client"), re-created 2024-Oct-16

downloadable from
or

changes and updates include:
1. account for day and month wrap issues for timestamped position
and Object reports.
2. support compressed-mode position reports for weather stations
where the compressed-mode position includes the wind direction
and speed.
3. speed up YAAC startup by optimizing initialization code.
4. properly identify private Objects as Objects when they will
never have any messages.
5. add ability to draw "heat map" of station position density
across time (for moving station coverage).
6. add optional capability to send an Object kill message when
a locally originated Object is deleted from the local system.
7. harden packet log import code to survive cases when logged
packets were corrupted.
8. add the ability to mark selected stations with higher or lower
importance for purposes of sorting stations.
9. fix cases where certain popup menu choices were not allowed on
the map view when they should have been.
10. remove some duplicate GUI layout code.
11. fix bug introduced in digipeat path editing panel.
12. widen timestamp columns in table views so the time isn't
truncated by default.
13. fix Object editor when updating an Object using an alternate
symbol table overlay code.
14. first pass at trying to fix Station/Object list when the list
is restricted to only Stations or only Objects.
15. first pass at trying to fix map refresh logic when timed values
need updating.
16. fix rendering of overlay character when using double-sized or
quad-sized icons.
17. add indicator on map window toolbar to report that filtering is
being used, so the user doesn't have to open the Edit->Filter
dialog to check for the presence of filtering.
18. fix inactivity timing in APRS-IS port driver to prevent spurious
disconnects when traffic is light.
19. make the "pool ball" icons stop rotating on the map.
20. fix ADSB plugin to refresh the map when aircraft data is updated.
21. make it possible to clear old history from the vessels table in
the AisDecoder plugin.
22. fix pseudo-APRS-IS server plugin to send cached state of known
stations to newly connected clients so they don't have to wait
to get current on network status.
23. update demo and smallscreen plugins to work with new screen
feature added to support a previous build's update to the
dynamic objects plugin.
24. add ability in dynamic objects plugin to locate the position
of a distance along a route.
25. tweak the MS150CueTranslator utility to match the identifiers
used for this year's rest stops.
26. add more icons for amenity types on the OpenStreetMap rendering.

You could do that on YAAC running on Mac OS X or Linux. However, because of the peculiar way Microsoft Windows binds virtual COM ports over Bluetooth, YAAC can't talk to the Mobilink over Bluetooth from Windows.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of David Alan Tibbetts via groups.io <cymru242002@...>
Sent: Wednesday, October 2, 2024 3:56 AM
To: [email protected]
Subject: [yaac-users] YAAC connecting with a Mobilinckd 4 tnc

I am the proud owner of a Mobilinkd 4 tnc Is it feasible to useful to connect it to YAAC. It's only drawback is that it is battery powered, as in a rechargeable battery, in fact I seen was curious about it's efficacy as a kiss tnC to connect to a MicroStat WX3N1. Thoughts on all of the above?