jks

So the problem here was a Kiwi purchased from a distributor that was old enough it didn't have the two boards (Kiwi, Beagle) held together via the two nylon standoffs. Vibration in transit was enough to separate the two header connectors such that the Kiwi board was not seen by the Beagle. The Beagle itself was working fine.

Re-seating the Beagle onto the Kiwi board was all that was necessary to get it working. But it took us a while to realize this had occurred.

Yes, because it makes no sense to try and register a Kiwi as being public when there will be no channels anyone can connect to!

If you want all your channels to have a password then presumably everyone who knows the password also knows how to get to your Kiwi.

The wording of that menu item is perhaps not 100% clear. But I couldn't think of a better way of saying it.

So I think the summary here is that there are routers that behave badly and the Kiwi code needs to be changed to accommodate that. Starlink after a power outage is another case. Apparently it takes forever for the terminal to acquire sats and assign an IPv4 address.

I've prototyped a VDSL "filter" to be used with the Kiwi SNR measurement (I used kiwirecorder for the prototyping). I works well for the one Kiwi I know about that has bad VDSL noise, causing it to have inflated SNR values.

If you know of other Kiwi's with this problem please comment here or email support@kiwisdr.com so I can try them out -- Thanks.

Basically, once the VDSL segment is identified it is excluded from the SNR measurement. Same as we have now for masked frequency segments.