The KiwiSDR 2 online store is open for orders! Please visit kiwisdr.nz
SDR not showing on listing
Hi, my SDR is 'registered', but is not showing on rx.kiwisdr.com
What else do I need to do please?
Thanks
Andy EI2HH
What else do I need to do please?
Thanks
Andy EI2HH
Comments
Also, is this simply a case of your ISP having changed your public ip address? (since you've taken no measures it seems to guard against that possibility).
Thanks
For example, from the Internet you can visit http://185.178.64.39:8073/status and get the correct response. But your Kiwi cannot contact kiwisdr.com at all because it can't even reach its own DNS server!
So this is not a Kiwi problem and you'll need to find your own solution.
Thanks for checking.
-Thanks.
In "enter shell command" below type "ping 8.8.8.8" or "ping kiwisdr.com" (or google.com or something).
Type control-C to stop command if no response.
Is your device running the browser on the same 192.168.10.xxx subnet as the Kiwi? That's what it is checking for.
If you are connecting to the admin page of a remote Kiwi over the Internet (i.e. not from the same local network as the Kiwi) then the "console" tab functionality is disabled as a security measure. The rationale was that if your Kiwi admin password was leaked or guessed then it would be better if all the bad guy could do was change your Kiwi configuration rather than also have Beagle root shell access.
The better solution is to use ssh as the transport mechanism for the admin console tab. I worked on that for a while but had implementation problems and never finished the work..
Is there anyway I can do a ping, or see if the outgoing route is working remotely?
How is the Kiwi registering if it cannot see the outside world?
Thanks.
I will try to check the routing in the router today.
Thanks for your help.
Attachments:
https://forum.kiwisdr.com/uploads/Uploader/ab/e1f363ae6ffca51f9aa1edf17b66d2.png
Thu Aug 20 17:26:29 10:14:12.510 0... _reg_kiwisdr_com: sp == NULL?So this particular error condition is not being reported properly on the admin page. The logs on kiwisdr.com show absolutely no incoming connections from this Kiwi's ip address (from the new remote location).
curl http://185.178.64.39:8073/statusAnd it will connect and return the expected data.But if you initiate even the simplest connection from the Kiwi (TCP SYN) it will stop dead on the second hop. I don't see that 10.x.x.x local network in the reverse (incoming) direction if I do a traceroute from the outside. This is definitely some horrible network misconfiguration. Is this site on the end of a wireless link or something? Who is airwire.ie? Is this their fault?
Traceroute to a well-known DNS server from Kiwi:
Traceroute from kiwisdr.com to Kiwi:
Kiwi connected to a Mikrotik LT AP (192.168.10.1), which has a cellular SIM. Because the cell company do not give a static IP, I have a VPN set up so the Mikrotik uses the cell connection to tunnel to the VPN server (at Airwire), which gives me a static public IP.
As I tried out on security tab set to enable restrictions on console on local to "no" and restart server should work.
However I am not familar with the specific syntax yet. Where to learn? Thx.
Are you asking what the syntax is for Linux shell commands you enter in the admin console window?
Well, that's not a topic we can teach you about here really. If you are new to an operating system like Linux, or a Linux distribution like Debian, then that's something you'll have to study yourself. It's a huge topic that has nothing to do with software radios directly.
Maybe I misunderstood your question?
Thanks for insight, but basically I do not know, wether I am "landed" on "root" correctly. How does the prompt looks like correctly. I presume the procedure will be similar to some router configuration. And of course, some commands in order to get on to the system memory (ROMMON) cannot performed remotely. The "send break" command for instance. On temninal programs like TeraTerm or PuTTy you can perform "send break" only connected physically to the console port of the router on working place. This prevents from misuse. On KiWi's console one uses the LAN-Port connected to local as a console port. This is a great advantage and prevents from potentially misuse.
For instance for some routers I have to change level from router#> to level lower by typing "enable". Only then I am on the programming level. If this is not necessary using KiWi, we do not have any concearn.
Okay, so I did misunderstand. Sorry.
The admin console tab always gives you a privileged root shell. Not an unprivileged one that you might get from a login to the "debian" account.