Find your Kiwi using

Got a Kiwi (running v1.330+) on your local network with an unknown local IP address? Like a new Kiwi out-of-the-box? Now from a browser on the same local network you can connect to and be automatically redirected to the Kiwi. The local IP address of the Kiwi will then show in the browser address bar.

This feature is similar to that provided by other IoT devices. It requires that the Kiwi have access to the Internet when it starts up. And that the computer running the browser is on the same local network as the Kiwi. If there are multiple Kiwis on the network the browser will display a table of Kiwis by serial number and a link that will connect to each one.

Our documentation lists 5 different methods of determining a Kiwi's IP address. But each has its limitations and disadvantages. Now there is a sixth method that is particularly convenient.

If you want to opt-out of your Kiwi sending this information to each time it starts then set the switch on the network tab of the admin page to NO: "Register this Kiwi on on each reboot?".

This feature has not been tested with IPv6 or mixed IPv4/IPv6 local networks. So there is likely some debugging required.


  • The multi-Kiwi page has been updated to also include a direct link to the admin page of each Kiwi in addition to the user page link.
  • edited January 2020
    I use Zeroconf to find local devices and services. That's a set of IETF standard protocols that originated as Apple's "Bonjour"; they're especially popular for discovering local printers. The KiwiSDR already runs 'avahi', which is the main Zeroconf daemon for Linux. (mDNS is just part of Zeroconf; that's how it responds to "kiwisdr.local".) If you create files under /etc/avahi/services, then it will also advertise those services so they can be found by a Zeroconf client like avahi-browse on Linux, the Safari web browser with the Zeroconf extension, or the third-party Discovery application on Mac OSX. I've attached the files /etc/avahi/ssh.service and /etc/avahi/http.service that I added to my KiwiSDRs. To get them past the forum's file name filter I had to append ".txt" to each one; remove before you place them in /etc/avahi.

    One advantage of doing this, rather than running only mDNS, is that you can still discover a KiwiSDR whose name has been changed from "kiwisdr.local". I have had to do that when there's more than one on my network.

  • Is it possible that an ISP could obstruct this kind of service?

    My kiwi is fully updated, has the correct switch set on the admin networking page ,and won't respond to the request, or to the kiwisdr.local one. It never has done. I just get a message saying No KiwiSDR(s) found for your public ip address:*******.

    As far as I know, everything is set up properly. It works very well in every other feature that I have tried. It's a bundle of fun. Glad I bought it. :smiley:
  • Are you using any kind of VPN?
    I.E. does the browser get to the internet through the same gateway as the Kiwi?
  • jksjks
    edited February 2020
    @Tony: last saw a registration for the service from your ip (ending in .214) and Kiwi serial number (ending in "1") on Feb 11. So unless your ip has changed I don't know why it wouldn't work. If you visit does it show your correct public ip?

    The MDNS/Avahi thing (kiwisdr.local) is unreliable when used from Windows. Sometimes it works, sometimes not.
  • jksjks
    edited February 2020
    Although our documentation doesn't currently say so, if you have multiple Kiwis on the same local network (using the default "kiwisdr" hostname) then Avahi will differentiate them by adding "-N" beginning with the second one. I.e. kiwisdr.local, kiwisdr-2.local, kiwisdr-3.local ...

    I just tried this again to verify it works.
  • jksjks
    edited February 2020
    @Tony: I just added some debugging code to the function that triggers on your ip address. Could you try it again please so I can see the debug output and try and figure out what might be going on? Thanks.
  • @Tony: Has your public ip changed from ending in .214? I just looked at the server logs for accesses to from your ip and I only see two attempts from Jan 31. Nothing more recent than that.

    As I mentioned earlier the only registration from a Kiwi for the service using that Kiwi serial number was from the .214 ip on Feb 11.
  • Sorry for the late response.

    Yes the IP address has changed again. We have been having winter storms and there have been some very short interruptions of power supply so I guess that may account for public ip address changes in the router as it is knocked over by the momentary power cuts.

    The debug page shows the correct, up to date address. I am using your proxy service for access outside the local network. That works fine so the kiwi must be logging in when it reboots.

    I have it set to reboot each night.

    Odd to say, but the command now works as it is supposed to. It REALLY wasn't working when I made that post.

    The other one, http://kiwisdr.local:8073/admin returns a message that the site can not be reached.

    I am mostly using a chrome book for access, also an android tablet and sometimes an android phone, though the only one I've tried the kiwisdr.local:8073 has only been used with the chromebook.

    No big deal John. I don't waant you to go to great lengths to debug this. I'm sure you have enough to do already.

  • What's probably going on is just a side-effect of the dynamic public ip address changes. Your Kiwi only registers for the service once when it boots. If your public ip subsequently changes then won't work because depends on matching the registered public ip with the public ip presented during the browser query. With some effort this could be fixed. But the service is really intended to help people with initial installation (when the registration and query would be closely spaced in time).
  • edited February 2020
    Thanks John. That's completely clear and explains the issue perfectly. It wasn't a biggie at all - I was just curious to understand it.

    By the way - I wrote previously about GPS difficulties caused by my weird location, sheltered from the sky. I disconnected the antenna and in a stable temperature environment, it doesn't matter at all. The thing is dead stable. I check it daily on WWV on 10 mhz and it has been dead on frequency for four days since I made the initial correction manually.

    Great product.
  • What does it mean when I get this message? I was just using it. It's there.


    Ken VE3HLS

    No KiwiSDR(s) found for your public ip address:

  • Hi Ken,

    I believe the message means that your router has not been configured to allow connections to the KiWi from the outside world via your ISP.

    When you say you were just using it, I assume you mean just using it on your own personal local network ?



  • Hi Ken,

    At some point did you see an entry for your Kiwi and then click the clear entry link? Because I see in the logs that your Kiwi registered for the service back on August 2 but does not now appear in the table for some reason.

    Try restarting the Kiwi and see if the entry shows up.

  • I have people using my Kiwi on a regular basis. It's setup for outside users.



  • Sorry, an entry where? I can tell you I definitely haven't clicked any Clear Entry buttons.



  • Ken: Okay. Please email your public ip address and/or Kiwi serial number so I can check the database. Also, please restart your Kiwi and let's see if it re-registers correctly.

  • Will do John.

    Just finishing breakfast here and will wander down to the shack after I scrape my teeth!


  • My Kiwi is configured to reboot once a day. A few users were having problems connecting and this fixed it. That said, I will manually reboot it as soon as it lets me back in.


  • HHmmm...I can't get back to my Admin page after several attempts. Maybe it's doing its automatic reboot now? It's 0327 UTC as I write this, within the 0000 to 0600 window my Kiwi mentions.

    Will keep trying.

    BTW, logging on to the Kiwi has become very slow in the last few days, taking a minute or more at times. The Kiwi connects to the router via ethernet LAN through a 4 port switch in my shack, and computers connect via wi-fi.


  • Finally got back in. Rebooted the Kiwi Server. Afterward, as soon as it got to the Admin page it booted me out again, to wait for another 60 seconds. This time, when I got back in I rebooted the Beagle. Just waiting for that now...

    My minute is up. Something else is wrong here because I'm into my fourth minute of waiting to log back to the Admin page following the eagle reboot.


  • jksjks
    edited August 2023

    So it looks like you're using the proxy service (even though not a publicly listed Kiwi). I didn't quite realize that. It's possible that the mechanism doesn't work when the proxy is in use. I'd have to do some checking. [edit: it does work]

    But I just got a big box of prototyping parts delivered for KiwiSDR 2. So I have to spend time on that. There are just not enough hours in the day..

  • That's exciting news about the KiwiSDR 2! Best of luck with that. I hope you're able to find someone who can assemble them.

    No rush on the other thing. I seem to be having my own problems with my Kiwi or my network. Can't access it from here...



  • Not sure I understand. Are you having problems making a regular user connection from your local network? Or is it the same issue as with admin connections -- you get booted within a few minutes?

  • It seems I'm only getting booted from /admin sessions, and not from listening sessions. I was getting kicked off every 2 minutes or so...

  • Now I see what I did. Dumb mistake. In my defense, there are so many settings in there that I'm unfamiliar with most of them. I've tried to keep quiet about my Kiwi, only letting a few groups know, because I don't want any problems from hackers and other ne'er-do-wells. That's why I would have turned off that setting. I didn't understand the full repercussions of doing that.

    I'll leave it on because it looks the exposure is minimal.

    Thanks again,

    Ken. VE3HLS

  • Ken is talking about the setting on the admin network tab: Register this Kiwi on on each reboot? (Yes/No)

  • is still saying no KiwiSDRs at my public ip address. Could that be related to the reverse proxy thing? I'll check tomorrow to see if it has my correct ip address. Would that be the address of our router or the address of the Kiwi itself?

    Ken VE3HLS

  • jksjks
    edited August 2023 is still saying no KiwiSDRs at my public ip address.

    Yes, I didn't change it because I wanted you to see that it was really set to "No". The entry now appears on as it should.

    When you visit it will show you the current ISP-assigned public IP of your router and DHCP-assigned local IP of the Kiwi. I note that the public IP is different from what you told me in email. And this is typical of ISPs where residential IPs are not static. Of course the real reason the proxy was needed was because your ISP disallows inbound connection setup (i.e. people connecting to your Kiwi directly).

Sign In or Register to comment.