Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
BlackList
|
YAAC's assumption for blacklisting is that you don't want to propagate the blacklisted station's traffic _anywhere_ (such as a station transmitting illegal traffic that you don't want to get blamed for forwarding). So, such stations' traffic doesn't get repeated through any port in YAAC (RF or Internet).
If you don't want to digipeat such traffic to RF, I'm not sure why you would still want to clutter the APRS-IS backbone with the traffic, as some other Tx I-gate might feel obliged to retransmit it to RF. In any case, YAAC doesn't have per-port blacklisting. You might be able to adjust your digipeat alias lists on your RF ports to exclude the alias the offending station is using (i.e., only do WIDE2-n if the offender is doing WIDE1-1,WIDE2-1 and you are the first hop). That is annoying that your offenders are over the normal duplicate suppression threshold (30 seconds) so that alternate packets from them wouldn't be dropped anyway. Perhaps I should look into the option of configurably raising that threshold; on the other hand, the offenders could easily work around that by simply putting a variable field (i.e., serial number) into the packet body so consecutive packets aren't duplicates. Have you tried to contact the station operators to suggest they slow their packet rates? Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of Pascal Charette Sent: Wednesday, October 7, 2020 1:43 PM To: [email protected] Subject: [yaac-users] BlackList Filter Blacklist work perfectly to stop digipeating fixed stations using 2 hop every 2 minutes. But would be nice when SSID is in Blacklist get i-Gate to APRS-IS. Because when SSID is in BlackList, it is completely ignored. Is there a way to do it? ve2pcq |
|
How does a blacklist correct the source of the problem? It can be used to stop your station from digipeatering, but it doesn¡¯t stop others from doing the same.? The problem still exists, you have just removed a small part of the issue. This is a good thing from your perspective, but still leaves the source issue in place.? It may lead to the source station increasing the number of hops to try and get to another I-gate if you blacklist his station in your I-gate. This means that the problem at the source station has gotten worse rather than better.? Blacklist him on all local digipeaters, and maybe he goes to higher power to get to a more distant digipeater that doesn¡¯t have him blacklisted.? Blacklists are a bandaid on a bigger issue.? Obviously trying to get people to understand the impact of their poor path/timing is a difficult thing to accomplish, but it is the best solution.? It¡¯s unfortunate that people don¡¯t invest the time to understand a technology before putting a station on the air.? On Wed, Oct 7, 2020 at 11:52 AM Pascal Charette <ve2pcq@...> wrote: Filter Blacklist work perfectly to stop digipeating fixed stations using 2 hop every 2 minutes. --
James VE6SRV |
|
In the past I realized to contact them was a waste of time, some don't understand. I just wanted to stop digipeating, like: a Weather station transmitting every 3 minutes using WIDE1-1,WIDE2-1.
And VE2PCQ-3 have a big coverage ;). I try APRSISCE/32, but many user wanted a Blacklist, but there is not. So I'm testing YAAC, I'm new with this one. |
to navigate to use esc to dismiss