jks

Well, this entire thing quickly becomes yet another SNR-related rabbit hole. One that I can ill afford at the moment given all the other important stuff I'm working on. I'm only doing it because of a person who is very unhappy the top NZ SNR score is due to VDSL noise.

I should have never added any SNR capability. The project has actually suffered because of it.

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.

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.

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

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.

By request: The resampling option now works with netcat and camping modes. Just update your kiwiclient clone to get the changes.

TDoA and kiwiclientd tested this time to make sure I didn't break them (hopefully, lol)

"/" is considered one of the keys that are redirected to the frequency field (also 0-9 . , : - # k M enter/return backspace/delete). And that must be terminated by an enter/return. Because instead of a plain "/" you could have typed "/low,high" or "/width" (passband specification) as the frequency field help shows.

From the admin console type: cdk; rm opt.debug and then restart. That will stop those additional logging messages.

@smg Running fail2ban would kill the Linux realtime response causing the audio to break up as the Kiwi server process becomes starved for CPU cycles. You can't run a heavy process like a Python interpreter at the same time. We are already extremely lucky that running kernel iptables filtering and user mode frp proxying doesn't cause trouble.

Wow, one of the few times the YouTube algorithm has recommended an extremely useful video.

In a few minutes I learned more about practical PCB RF design than I ever knew. Very easy to understand: https://www.youtube.com/watch?v=xhuHAhIKWoM

Should be better if you restart to get v1.815