n6gn

FWIW, I had very similar symptoms when Comcast/Xfinity (US cable ISP) changed to a new on-line administration tool for my router. They 'kindly' added something that must be akin to an iptables entry at their gateway which flagged all the kiwi traffic as 'malicious' or a threat and blocked it. I got the same error as you. This seemed to come and go, per some algorithm that I couldn't discern. After several hours on the phone (with someone in the Phillipines) I found the sub-menu on the web site which let me revert the security settings to avoid them shutting down access.

I don't know if this is related to your cause or not, but I thought it might be helpful.

Glenn n6gn

Claire,
The steps I gave before seem to have fixed the problem for me. I am not an expert in this area either but no one has yet commented that there is a better way. To accomplish the block I first logged into my kiwi as root. I did this using secure shell, ssh, on a Linux host but this is also possible from a Windows machine via PuTTy or similar. Using PuTTy, simply enter the address, port 22, and it should then ask you to OK the connection. After you do, it will ask you who you want to log in as. Answer 'root'. That should get you a command line prompt from the kiwi. Once logged in I executed three lines:

iptables -I INPUT -s 47.88.219.24/24 -j DROP
iptables -I INPUT -s 184.22.160.13/24 -j DROP
iptables-save

There may be even easier ways but that's all I did and it seems to have worked, the log is no longer reporting these hits. Presumably these could start again from a different IP address and I would need to repeat one of the above first two commands with that address in place of the one shown.

Glenn n6gn

Martin,

Thanks for documenting this. From my observations, mainly at HF, the 20-30 MHz noise that is endemic with Kiwis has a vector into the kiwi via CM noise on the LAN connection/lines. I think this is what you were addressing with the CAT5 shield, though it is still possible to get TEM ==> CM conversion on a long cable even with shielding, depending how it is configured. Current injected on the far-end shield can still end up inside the box.
Often this QRN manifests as a family of ~60 kHz separation lines in the 20-30 MHz region. Rob, AI6VN has had good success in mitigating these, without additional enclosure shielding, through use of a USB/WiFi dongle which bypasses the wired LAN connection and attendant spurious energy. Perhaps he will post some documentation of that as well.

Best,
Glenn n6gn

I recently received a KiwiSDR from Mass Drop and made some measurements of distortion and noise of the unit. These measurements and their results are detailed in the attached file.

Glenn n6gn

I recently received a KiwiSDR from Mass Drop and made some measurements of distortion and noise of the unit. These measurements and their results are detailed in the attached file.

Glenn n6gn