For a few days now I have noticed that the k5ede station created as a webtransceiver connects to our node hub and connects hundreds of nodes. How can I ban it and force it not to connect to our node hub?
Did you try this?
It is not a node but a user, I assume with webtransceiver access through registration from allstarlink.org, in any case I do not understand how a user can connect and disconnect other nodes to our hub.
That account has been disabled; the actual callsign holder has been in contact and he never opened the account.
To block a user through the deny list, since they are ID'd with a call sign and not a node number as a web transceiver,
you need to modify the section of the dialplan for it.
For they are ID'd as callerid 'name' and not 'number'.
I did present a solution for this in some other thread just a few months ago.
Perhaps they will incorporate that or something like it in future version.
But no stopping anyone from DIY.
But probably not a good idea to call someone out in a post by name or call here.
The title will be modified 'this time'.
Our 3.5.x set of packages, currently out for beta testing, allows you to add callsigns to the node access list (app_rpt Issue #690). The changes update both the asl-menu "Node Settings" and the dialplan.
2 Likes
You could change the DTMF commands and or command prefix.
For example to change the * prefix to *234 set inxlat = *234,#,0123456789ABCD in your rpt.conf. Now the disconnect command would be *2341<node> instead of *1<node>.
Docs for inxlat rpt.conf - AllStarLink Manual
Let us know if you have questions.
You can go on allstarlink.org and under portal and Node settings turn off Web transceiver that will stop them from coming through that way. Otherwise, you will have to set up a deny list to ban him from it. You can also look up his call sign and send an email telling him from refraining from ever doing it.l