n6gn

Actually, I think the power has been on the whole time. The issue seems to be a poor quality router that loses its way and no one having access to help it out. There may be plans for a replacement but there is perhaps a little politics in that one. Perhaps Rob may be able to elaborate.

I'm finding that "it works sometimes". I managed to get it not work, QSYed to a ham band where it worked, fussed around after which it quit. Maybe someone else can figure out the conditions for (non)working.

@HB9TMC
I haven't documented the kiwiSDR onboard GPS performance but I have examined it, particularly in comparison to use of the Kiwi with an external clock. You can do the same by comparing two of my kiwis, one with a Bodnar GPSDO which generally appears to be better than 1 ppb and to not limit the phase noise performance of the kiwi with another using the on-board GPS reference.
Bodnar referenced Kiwi
and
on-board kiwi GPS
are both looking at US NIST LOS/"groundwave" signals transmitted from less than 20 km distant.
This may not be entirely satisfactory since the on-board kiwi's GPS antenna is outdoors but not very well located.

I think many of us find the low end not dark enough and routinely adjust it to dark blue. jks has mentioned this too, I think.

In a kiwi itself rather than my router, after trying it with FORWARD, I ran:
iptables -I INPUT -s 47.88.219.24/24 -j DROP
iptables -I INPUT -s 184.22.160.13/24 -j DROP
since I'm trying to stop packets from two different offenders at the kiwi rather than from being forwarded by the router. This I followed with:

iptables-save

so that it will (I hope) get restored upon reboot. Examining the results I get:

root@kiwisdr:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
DROP all -- 184-22-160-0.24.nat.tls1a-cgn02.myaisfibre.com/24 anywhere
DROP all -- 47.88.219.0/24 anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
DROP all -- 184-22-160-0.24.nat.tls1a-cgn02.myaisfibre.com/24 anywhere
DROP all -- 47.88.219.0/24 anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

I'm not familiar enough with iptables yet to know if this will be sufficient, perhaps only the INPUT rule is needed. Maybe someone who knows can suggest whether this is correct or whether there's a better way.