[arm-allstar] Blacklist
Patrick Perdue
borrisinabox at gmail.com
Mon Nov 27 17:11:35 EST 2023
It's also worth noting that a blacklist on your node won't have any
affect if someone comes in through another connected node, since it's
that node making the connection to yours, not the problematic node itself.
If the [blacklist] context is configured properly, and a node has been
added to the blacklist database, it should refuse connection with a match.
However, if, say, the other repeater with a public port has no blacklist
configured, and they're getting in that way, they're still on your system.
So, make sure everything that can accept connections has a working
blacklist, and that your problem node numbers are common to all of them.
On 11/27/2023 3:01 PM, ve3rwj via ARM-allstar wrote:
> If the person is connecting using web transceiver (WT), using RepeaterPhone, Transceive on the Mac, etc. they aren't going to have a node number associated.
>
> Is there a way to block callsigns?
>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
More information about the ARM-allstar
mailing list