jks

Although I think public Kiwis with ham-band-only frequency masking is kind of annoying, I've had several requests to make this easier to setup. So in the documentation describing the feature there is a .json or .csv file you can use with the admin/DX tab "Import JSON/CSV" button to do so: http://kiwisdr.com/quickstart/index.html#id-user-marker-masked

No. Didn't want to make things quite so easy for China.

From the CHANGE_LOG file:

v1.682 fixes the problem reported by @HB9TMC where ipset/iptables wasn't filtering properly (but the Kiwi server was as a backup).

But I also noticed something important. On the admin network tab, the "local blacklist" section where you can enter your own ip addresses and ip ranges: Be careful to not enter invalid or duplicate entries. Especially duplicates. Because processing of the local list will terminate at the point it finds a duplicate. It's a pain for me to detect this condition and report it back to the admin interface. I have much more important things I need to be working on. So this warning will have to suffice.

Consider this local blacklist entry:

There are two problems here. 217.150.74.0/16 is deceptive because the /16 means the bottom 16-bits are considered the wildcard host address part and should really have been specified as 0.0 as in 217.150.0.0/16. That means the following 217.150.75.255/16 is also wrong and also considered as 217.150.0.0/16. Hence two identical entries in a row causing an error which prevents the 5.6.7.8/32 entry from being added to the blacklist!

So be careful when constructing your lists. Use a site like https://www.ipaddressguide.com/cidr to check your IP range for proper CIDR representation.

You only have 3 sats in the az/el display which is the bare minimum to maintain a lock (assuming they're strong enough to be tracking & decoding properly).

What happens if you turn off GPS, do a manual calibration, and just let it free-run?