jks

I see those occasionally and don't quite understand them. But I also haven't spent any time trying to track them down. My guess would be some buffering problem where a configuration save command from a prior admin session is leftover someplace and gets flushed out to the Kiwi during the next connection (the arrival from China in this case). I don't believe anything malicious is going on here.

October 7/8: Massdrop is active again for 7 days. $80 discount on the Kiwi kit ($219 vs $299). Free (but slow) shipping to the USA. Best deal out there. Limited quantities available and over 70 people were on the notification list. So don't delay.

@Kevin Not a problem at all. What led me straight to the bug was the report in the other thread: click the "kick" button on a WSPR auto-run connection and the server crashes.

Okay, I see the bug. It was actually introduced in v1.235 but doesn't get triggered until a restart (like when updating to v1.236)

I'll fix it in today's update. But the issue now is that you'll either have to temporarily turn off WSPR auto-run or go through the manual update procedure one more time to get past this problem.

The "git pull" is a little redundant. But it won't hurt anything. You must login to the Beagle as user "root" and not "debian". Contents of "up" file, in part:

make stop
git clean -fd
git checkout .
git pull -v
make clean
make
make install
make start