[arm-allstar] Blacklist
David McAnally
david.mcanally at gmail.com
Mon Nov 27 16:02:21 EST 2023
On Mon, Nov 27, 2023 at 11:38 AM Rich Schnieders via ARM-allstar <
arm-allstar at hamvoip.org> wrote:
> I manage a small slinked repeater system consisting of 5 repeaters and a
> few simplex nodes. All the repeaters and nodes automatically link to a
> radio-less hub. Only the hub and one repeater have public ports exposed to
> the internet. We have an issue of a young ham who used to live in our area
> who links his own node to our hum and then plays music, uses vulgar
> language
> and disrupts ongoing communications on the linked repeaters.
>
> I have added his callsign and nodes to the blacklist following the
> instructions here:
> https://wiki.allstarlink.org/wiki/Blacklist_or_whitelist
> but he still can link to the hub. I seem to have missed something. I have
> modified extensions.conf, iax.conf, as directed by the above directions.
>
> Any suggestions would be appreciated.
>
Did you also modify the [allstar-public] context for web portal (web
transceiver) users as described at the bottom of the blacklist/whitelist
instructions page? Alternatively, you could try disabling web transceiver
access for your node number in allstarlink.org node settings.
As far as I know, any ham with an authenticated allstarlink.org login
account can use the web transceiver mode via apps like DVSwitch (Android
app) or Tranceive (Mac app). They will connect with their call sign as
registered with Allstar, instead of an assigned allstar node number. Node
owners can enable or disable web transceive access to their nodes via
allstarlink.org settings.
David McAnally
WD5M
More information about the ARM-allstar
mailing list