Easy user ban
Feature request:
On the Status admin page, next to the Kick button, add a Ban button which automagically adds that user's IP address to the local ban list.
As a bonus, then also kick the user.
It looks like you're new here. If you want to get involved, click one of these buttons!
Feature request:
On the Status admin page, next to the Kick button, add a Ban button which automagically adds that user's IP address to the local ban list.
As a bonus, then also kick the user.
Comments
It's tempting, but it's better to be patient and tolerant, as it's easy to make a mistake... Paradoxically, my local blacklist contains over 70 addresses, including several entire blocks. I watch someone like that for even a month, and even if they use multiple IPs and names, you can sometimes glean some useful information.
When I've got the same bozos sitting on 11175 USB day after day, for hours, sometimes dozens of hours (the record so far is something like 56 hours straight), it's not a mistake.
And yes, I know you can set time limits, but I try to avoid that as some users have legit reasons for extended time periods. As is often the case the reason "we can't have nice things" is to due a handful of people misbehaving. (Sorry if this sounds like a rant, I just booted two of them off the KiwiSDRs)
You could mask that frequency for awhile to deter those repeat offenders. It's possible some of these people are re-streaming the SDR on YouTube like people do with the Russian buzzer.
For a long time, I masked all traffic outside the amateur/utility/AM bands, and for about three years, I was able to identify networks whose channels were still occupied despite being blocked. The pool is twice as large as the official blacklist, mostly containing cloud services, VPNs, free proxies, and the most problematic networks. For several months, I've been blocking only a few spots on the spectrum, and the number of leechers has dropped to almost zero. They appear occasionally, of course, but when I occasionally review the logs, I systematically add them to my extensive list. If anyone wants, I can post it here.
Hi Chris,
I find the inactivity timeout to be the most useful, and very rarely have to block frequencies. Although when I have been forced to do so, it only seems to be required a few days.
The timeout requires some user interaction to maintain a session, so anyone actively listening, rather than just running the KiWi in the background, shouldn't be affected.
I use a 15min inactivity timeout, and a 120mins per day IP limit, which seems to achieve a reasonable degree of fair use.
I have given a few trusted people a password to override this, but they are actively contributing logs to various groups, and act responsibly.
Regards,
Martin