Blacklist not working as expected #188

Closed
opened 2026-10-05 05:47:12 +02:00 by adam · 11 comments
Owner

Blacklist not working as expected

when adding a call sign to the blacklist as specified it does NOT block it.
I found the solution but this is not as intended.

First add callsign to black list
example : AB2CDE* HJ4WSE-5 XY6Z*
press save and reboot

then disable all these options :
enable aprs-is connection
gate aprs-is message to rf
gate aprs-is objects to rf
enable lora TX
enable lora RX

Yes you read it right ! DISABLE THEM
press SAVE and reboot

allmost done ... enable these options again .. so ENABLE :
enable aprs-is connection
gate aprs-is message to rf
gate aprs-is objects to rf
enable lora TX
enable lora RX

press SAVE and reboot

Now youre black list is working
Please fix this , many thanks in advance

73

Blacklist not working as expected when adding a call sign to the blacklist as specified it does NOT block it. I found the solution but this is not as intended. First add callsign to black list example : AB2CDE* HJ4WSE-5 XY6Z* press save and reboot then **disable** all these options : _enable aprs-is connection gate aprs-is message to rf gate aprs-is objects to rf enable lora TX enable lora RX_ Yes you read it right ! DISABLE THEM press SAVE and reboot allmost done ... **enable** these options again .. so **ENABLE** : _enable aprs-is connection gate aprs-is message to rf gate aprs-is objects to rf enable lora TX enable lora RX_ press SAVE and reboot Now youre black list is working Please fix this , many thanks in advance 73 <!-- github-sync-id:2889757126 -->
adam closed this issue 2026-10-05 05:47:12 +02:00
Author
Owner

hi @PA9MWO , this is really strange as the writing process of saving the configuration to internal memory has nothing to do with having or not aprs-is switches enabled or not.

when you save the data (without your special process) do they get saved into memory? (do they appear after reboot written in the blackList box?

hi @PA9MWO , this is really strange as the writing process of saving the configuration to internal memory has nothing to do with having or not aprs-is switches enabled or not. when you save the data (without your special process) do they get saved into memory? (do they appear after reboot written in the blackList box? <!-- github-comment-id:2692937214 -->
Author
Owner

hello Ricardo
Yes ... sometime its getting written sometimes it doesn't.
I cleaned my Lilygo Lora32 1.6 completly ( with esp tool ) and reflashed it.
clean config installed.
I left it running this night and this morning i see the black listed has not picked up.
The item i put in the black list is not working.

There is a guy in my neighbourhood that is not a HAM radio guy and is illegaly using a fake callsign. :-(
I just want to block / black list him

i hopes this helps.
73

hello Ricardo Yes ... sometime its getting written sometimes it doesn't. I cleaned my Lilygo Lora32 1.6 completly ( with esp tool ) and reflashed it. clean config installed. I left it running this night and this morning i see the black listed has not picked up. The item i put in the black list is not working. There is a guy in my neighbourhood that is not a HAM radio guy and is illegaly using a fake callsign. :-( I just want to block / black list him i hopes this helps. 73 <!-- github-comment-id:2693342033 -->
Author
Owner

Ok ! I also filtered the (illegal) callsign in the APRS-IS filter. Thats ok for now.
But as i am a huge fan of sharing my info can you add an extra blacklist or filter
Yes i want to share all my recieved stations with lora.link9.net but not the illegal ones.

can you please add a filter in the syslog part ?
Many thanks in advance
73 pa9mwo

Ok ! I also filtered the (illegal) callsign in the APRS-IS filter. Thats ok for now. But as i am a huge fan of sharing my info can you add an extra blacklist or filter Yes i want to share all my recieved stations with _lora.link9.net_ but not the illegal ones. can you please add a filter in the syslog part ? Many thanks in advance 73 pa9mwo <!-- github-comment-id:2693943791 -->
Author
Owner

the blacklist process does block the "blacklisted" stations to be repeated and uploaded into aprs-is.

will have to check if this also blocks them to be sended into syslog.

beside this , where do you see the black list not working? showing them as received packets?

the blacklist process does block the "blacklisted" stations to be repeated and uploaded into aprs-is. will have to check if this also blocks them to be sended into syslog. beside this , where do you see the black list not working? showing them as received packets? <!-- github-comment-id:2694031748 -->
Author
Owner

Yes ricardo
Step 1 .
you have said "does block the "blacklisted" stations to be repeated and uploaded into aprs-is."
Thats correct ! Thanks for that.

Step 2.
But... I see the (illegal) callsigns popping up in the "Received packets" tab .
All whats in there is send out to the syslog server .
All this info is on the website : https://lora-aprs.live/
I just want to block the illegal ones there too.
So currently i switched the syslog option off.

I hope its clear for now.
thx in advance
73

Yes ricardo Step 1 . you have said _"does block the "blacklisted" stations to be repeated and uploaded into aprs-is."_ Thats correct ! Thanks for that. Step 2. But... I see the (illegal) callsigns popping up in the "Received packets" tab . All whats in there is send out to the syslog server . All this info is on the website : https://lora-aprs.live/ I just want to block the illegal ones there too. So currently i switched the syslog option off. I hope its clear for now. thx in advance 73 <!-- github-comment-id:2694055478 -->
Author
Owner

now I get this problem

will add this blacklist method to avoid showing it on Rx Packets and on Syslog packets too.

now I get this problem will add this blacklist method to avoid showing it on Rx Packets and on Syslog packets too. <!-- github-comment-id:2694061346 -->
Author
Owner

Youre the best ! Thanks man !
73

Youre the best ! Thanks man ! 73 <!-- github-comment-id:2694063788 -->
Author
Owner

Please download the code from github (not on webflasher still) to test it

it should block over the hole process any blacklisted station:
no digipeater packet
no upload to aprisa
not shown on Rx packets
not logged over Syslog

Please download the code from github (not on webflasher still) to test it it should block over the hole process any blacklisted station: no digipeater packet no upload to aprisa not shown on Rx packets not logged over Syslog <!-- github-comment-id:2694571697 -->
Author
Owner

I will test and keep you posted !
.. thx in advance

I will test and keep you posted ! .. thx in advance <!-- github-comment-id:2694700910 -->
Author
Owner

YES! great work !
the illegal stations are no longer available in the recieved packets and https://lora-aprs.live/ webpage.
many many thanks !
! issue solved !
73

YES! great work ! the illegal stations are no longer available in the recieved packets and _https://lora-aprs.live/_ webpage. many many thanks ! **! issue solved !** 73 <!-- github-comment-id:2694778749 -->
Author
Owner

great, adding this to new release then ;)

great, adding this to new release then ;) <!-- github-comment-id:2694783436 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/LoRa_APRS_iGate#188