Register Kiwi SDR online
Hello, If I register my Kiwi sdr online will I still be able to access it if all channels are being used and can I take it offline at anytime ? Is it safe to use the serial number.proxy.kiwisdr.com address or should I change it.
Any help would be appreciated.
Comments
If all channels are full you'd have to "kick" a channel via the button on the admin status page to create a free channel for you to connect.
Alternatively, you can reserve one of the channels by setting a user password on the admin security tab and then set "number of channels not requiring a password even if password is set" to 3 (assuming you're using 4-channel mode). Then that channel will always be available for your use. You won't have to actually give the password if you're connecting from the local network.
You could also use the "camp" interface to wait in queue for a free channel to become available if you don't want to permanently reserve a channel and don't want to kick someone. But you will be waiting an arbitrary amount of time in that case. The camp panel appears automatically when you attempt to connect when all channels are full.
It's fine to use the default serial number as the Kiwi name for a publicly listed Kiwi. Lots of people do that.
Many thanks, there seems to be so much to look at with so many tabs on the admin page.
Well, the complexity is a result of people asking for features over the years. That's the trade-off. I try and limit it as much as I can. It's a thankless task, as some people are always unhappy..
"Many thanks, there seems to be so much to look at with so many tabs on the admin page."
There are so many user cases that it's difficult to cater for everyone. But the more you use your KiWi, the more thankful you will become that a specific feature has been included in the admin setup.
I run several different types of web sdr, and the KiWi is the one that has incorporated the most useful features and suggestions from users and admins alike.
Many other developers will simply ignore such requests, because they personally don't understand the requirement, or simply focus on the software, rather than the needs of the users.
Some other web sdr's, require you to be a Linux guru before you can get up and running, so the KiWi is pretty much "plug and play" in comparison.
Regards,
Martin
Is there a trick to making a remote site visible on the list of public sites?
My remote receiver has generally been visible at http://22332.proxy.kiwisdr.com:8073/ but isn't showing since yesterday (it may have disappeared earlier, but I only noticed it yesterday). I was doing some work at the site, eliminating some RFI (some good improvements, but still some garbage to clean up), and noticed it wasn't visible on the public list.
Locally, I was able to browse to it over the LAN, and on the admin page I forced it to register again, which it said was a successful registration, but still not visible.
Any ideas on what to try remotely? Otherwise, any suggestions to try when I visit the site again in a couple of weeks' time?
Thanks & 73,
Chris
Hi Chris, @VK6KCH,
Your Kiwi seems not to be reachable. A router configuration problem probably.
Could you, please, go to Admin/Network tab and click on "Check port open button" and see the answer ?
Do you use the "Auto add NAT rule... YES" (same admin tab) or do you configure your router manualy ?
(True specialists will come to help you soon ! 😉)
73, Thierry
... and you can try a "KiwiSDR server restart" on the Admin/Control tab, do again the "Check port open", and see if your Kiwi appears on the list...
As Thierry mentions this seems to be a problem with inbound traffic. Not just inbound connection initiation, which the reverse proxy overcomes. But all inbound traffic.
I can see the Kiwi register for public access and the proxy service. But then nothing more. Proxy connections don't work. The proxy log shows it last worked when the public IP ended in "187". Now it ends in "66". The rest of the public IP is the same. So that's strange. Why would just changing the last octet cause all inbound traffic to stop? Again, use of the proxy means there doesn't have to be explicit NAT forwarding in the router. Yet there is no traffic flowing..
Hi John and Thierry,
Thanks for your replies. The KiwiSDR is behind a 4G router, so there's a stage of outbound NAT there (with no explicit port forwarding to handle inbound connections), and then on top of that, the 4G router is only assigned a CGNAT IP address, so there's another stage of NAT occurring on the cellular service provider's edge. I had assumed that only outbound TCP sessions would work, and that attempts to initiate inbound traffic (TCP or UDP) wouldn't work, thanks to the NAT barriers (especially the cellular service provider's edge)... hence the beauty of the proxy service! It was all working fine up until recently, so the overall architecture is viable.
I suspect that an outbound TCP session from the KiwiSDR to the proxy server has collapsed and not been reestablished? Or, is it even a UDP "session", rather than TCP? (I'm now wishing that I'd inspected the traffic with wireshark earlier, but I was focused on the RF side of things).
In the short term, I'll just have to hope it fixes itself, but I'll try to get back to the remote site in the next week or two and try rebooting the KiwiSDR whilst keeping the 4G router powered up. (I wonder if the issue was caused by the whole system being power cycled as part of the changes I was making, and a race condition being entered that has messed up the NAT table, especially as the 4G router has a habit of connecting to the cellular network for about a minute, then disconnecting and reconnecting again soon after... did the KiwiSDR establish the outbound NAT during the first short connection window, but it's not honoured during the currently established connection?)
In the longer term, I wonder if there's a way that the KiwiSDR can detect that the connection to the proxy service is a bit of a zombie, and then clear it down and rebuild it, or even force a complete reboot, to try to reestablish service? (If that feature is enabled... don't want to be rebooting any completely standalone installations that are only meant to be used locally!)
73,
Chris