Blocking messages from a Callsign
|
James Ewen
Greg, you've been around enough to know that not everyone understands that the APRS frequency is a shared resource, and that the best way to utilize the resource is via fair and equitable use of the resource. There are some who feel that everyone on RF within a hundred miles needs to know the temperature in their backyard every 5 minutes. There are those who think everyone needs to know where their vehicle, or worse yet, their house is located every minute. There are those who feel that they need to run a digipeater from their house that blasts out packets on a horrifically fast schedule using WIDE1-1 as a requested path. Education is much like trying to make the horse drink that you led to water. One must be receptive to the instruction, one must also understand that perhaps their station configuration isn't optimal, and finally one must undertake the work to optimize their station configuration. That's a lot of steps. How many people join this reflector, and start out with something like this: "Hi, I'm brand new to APRS... I want to set up a digipeater/i-gate at my house. How do I do that?". First baby steps should be figuring out how to set up an APRS station, and then spend time listening to the frequency and learning about the RF environment in the area. If one lives on an isolated island in the middle of the ocean with no other APRS stations for hundreds of miles in all directions, then jumping in and setting up a digitpeater/i-gate right away might be acceptable. However most people asking these questions live in an area with an established APRS network in place. I do agree that education is a better route than trying to ignore the issue. That station causing problems on RF can be causing problems for everyone, and just ignoring them doesn't help the rest of the network. The problem is that the amateur airwaves are open to all, and there is no legal means of inhibiting the TX capabilities of a station that is operating within the bounds of their license, whether you like it or not. Peer pressure is probably the only means we have of affecting change in APRS operations. Unfortunately, APRS operations are a type of use case where one can operate their equipment in almost complete isolation, especially if one is running a TX-only tracker, or never looks at any messages sent to their station. One just needs to set up the equipment, and then let it run. What's monitoring your equipment for proper operation all about anyway? I expect that Lynn does not implement any means of ignoring stations because he believes that ignoring the problem just leads to a degradation of the APRS network as a whole. But having said that, we have the ability to ignore Mic-e status messages... special, priority and emergency status messages should not be ignored, yet we can. Ever try and convince an APRS operator that they are not "special"? Education is better than ignoring, but it takes much more effort to educate. James VE6SRV On Mon, Jan 9, 2023 at 1:25 PM Greg Depew <goatherder_4891@...> wrote:
|
|
|
|
Greg Depew
Why would you want to block someone anyway? If they are doing something they shouldn't be, why not educate them on the proper way instead of just hiding the problem?
KB3KBR Greg. Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: Bob Davet <davet354tfd@...>
Date: 1/8/23 16:18 (GMT-05:00)
To: APRSISCE@groups.io
Subject: [APRSISCE] Blocking messages from a Callsign
Did a search for this but it is not showing what I want. W8RID |
|
|
|
Hi Bob. I can see you have figured it out in the meantime (with a bit of help from James). Page 10 in the manual, even though exclusions in APRS and ham world in general are not encouraged. But, sometimes there is not much option. I also have a callsign in that section for some time now.
73 de J, M 0 IPU, YO 3 FCA. |
|
|
|
James: Manual? We don't need no stinking manuals? Bob W8RID |
|
|
|
James Ewen
I don't use the software, but I downloaded the current manual and had a look at it. Search for the term "exclude". You can put the exclusion term into the .ini file, and that looks like it could be used to block any traffic from a specific station. Yes, sometimes we have to break down and read the user manual... :) James VE6SRV On Mon, Jan 9, 2023 at 9:12 AM Bob Davet <davet354tfd@...> wrote:
|
|
|
|
Julian: W8RID |
|
|
|
Hi Bob. If you're using Direwolf or UZ7HO RF soft modems you can block it there.
73, J, M0 IPU, YO3 FCA. |
|
|
|
Lynn Deffenbaugh
No, APRSIS32 doesn't support blocking anything in particular. However, if you're an APRS-IS-only station, you can possibly do it with a filter. Try adding -b/<OffendingCallsign> to your Configure / Genera/ Add Filter specification. That will ask the APRS-IS server to not send you any packets from the specified (explicit station like KJ4ERJ-12 or wildcard like KJ4ERJ*) callsign. Note that this will block all packets from that/those calls, not just messages. If you're receiving the messages via RF, APRSIS32 will process
them no matter what you configure where. Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/8/2023 4:18 PM, Bob Davet wrote:
|
|
|
|
Did a search for this but it is not showing what I want. W8RID |
|
|