I am upgrading my Kiwi in Thailand now. Everything went fine up to step 3.
I have found it's serial no in the network screen. But with: "ssh debian@192.168.0.104" (which is confirmed as my Kiwi's local ip), it's serial no is NOT any longer accepted as the password (the serial no was accepted at the earlier steps, when I started with this). Because of this I am not able to restore the old config files from my backup ssd (with debian 8.5) which I made before I started.
Re-flashing from the Debian 10 sd card, that has v1.486 on it, should have default account passwords. And v1.486 (or v1.661 for that matter) should have detected this and changed the passwords to the serial number. Don't know why that wouldn't have happened..
GPS: acquire pause, track 0, good 0, fixes 0 --- (Note: ok, antenna and gps not connected)
SNR: All 2 dB, HF 2 dB
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0
I also got a "communication error" when I tried to upload a new photo file. That I haven't seen before.
Photo fileUploading...
Communication error
Perhaps my debian has gotten corrupt somehow.
Right now I am trying a forced (normally unnecessary) "upgrade" from v1.661 to v1.661 to see if that fixes things. If not, I think I need to make a new debian 10.11 image (flash the card again) and scrap the old 10.11 one.
Update: The "communication error", photo problem fixed itself. Kiwi is online now with the correct config files and a new photo file, but the temppwd is still needed on ssh. For now I let it run as this.
Yesterday I was going to try and download an image again, and was having difficulty locating the correct image. In the past it would not upgrade from the 1.2 version, but you did mention that you fixed that, so I decided to give it a try. I let it sit overnight and the next day I discovered that it did upgrade by itself. it is now running 1.665, Debian 8.5.
Yes, there was a period of time after the Debian guys moved Debian 8 onto the "archive" repo servers that v1.2 got stuck trying to update. I thought all was lost until I figured out that /etc/apt/sources.list needed to be updated (the Kiwi Makefile now does this for D7/8/9). A lot of this stuff I don't understand very well..
My KiwiSDR is on the fritz again. This time with a different problem. I wish I could hook up a monitor and keyboard and see what the problem is. I am frustrated. But I like the Kiwi alot. I am ready to purchase another one when there is new stock next month.
No KiwiSDR(s) found for your public IP address: xxx.xxx.xxx.xxx
If necessary, temporarily disable any VPN or private relay service for this computer
(the one running the browser) so your actual public IP address can be found.
If enabled, a Kiwi registers itself on my.kiwisdr.com whenever it restarts.
My router does not see the Kiwi.
I get the blue cylon lights back and forth, and all also all blue lights blinking at the same time. Was thikning maybe it wa my power supply again. Tried another power supply, 5V 3A. Still didin't work. Tried doing a restore from my previous image backup. Didn't help either.
Okay, please do. That way I can check for any evidence on my end of what your Kiwi might be doing.
Also, it might be useful if you could try decoding the pattern in the 4 blue LEDs to verify the local IP address. It's a painful process unfortunately. Documented here: http://kiwisdr.com/quickstart/index.html#id-leds
If there is ever a Kiwi-3 I'm going to use one of those little 1.9" OLED displays to show the IP address etc. in text form. A much better way to go.
I have determined that the issue is with the new Linksys router I installed recently. I tried my old Linksys router again and the Kiwi works just fine. I am guessing it has something to do with the router using ipv6 to connect to all of my devices. Whereas my old router showed all the IPV4 addresses of my connected devices, my new router shows IPV6 addresses. It would have been ok with me since all my other devices connect just fine, just not the Kiwi. I was on chat with Linksys Customer Service for over an hour trying to get them to tell me how to force my router to use ipv4. I already found the tick mark for disabling ipv6 but that did not do anything. They are telling me to reset and reconfigure my router. The router doesn't even have a way to back up to a file. I'm going to turn off and on my router now. If that doesn't work I'm going to reset the router, and if that doesn't work I'm returning the router to Amazon.
Comments
I am upgrading my Kiwi in Thailand now. Everything went fine up to step 3.
I have found it's serial no in the network screen. But with: "ssh debian@192.168.0.104" (which is confirmed as my Kiwi's local ip), it's serial no is NOT any longer accepted as the password (the serial no was accepted at the earlier steps, when I started with this). Because of this I am not able to restore the old config files from my backup ssd (with debian 8.5) which I made before I started.
Is there a way around this?
The debian account password might still be the default
temppwdor the Kiwi admin password.Update tab:
Installed version: v1.661, built Feb 5 2024 06:27:07
Running most current version
Should I just wait a bit more then?
I came in with temppwd 😊
Re-flashing from the Debian 10 sd card, that has v1.486 on it, should have default account passwords. And v1.486 (or v1.661 for that matter) should have detected this and changed the passwords to the serial number. Don't know why that wouldn't have happened..
I'll wait a bit and see if it updates. If not, I can try booting from the deb.10, 1.486 card again.
If none of the above will work, perhaps I should try making a new image on the 1.486 card again.
v1.661 is the most recent version. But does the admin status tab say you're now on Debian 10?
Yes:
KiwiSDR 1, v1.661, 4 SDR channels, 12 GPS channels | Uptime: 0:08:47 | UTC: 09:17 | Local: 16:17 Asia/Bangkok (ICT)
Debian 10.11
GPS: acquire pause, track 0, good 0, fixes 0 --- (Note: ok, antenna and gps not connected)
SNR: All 2 dB, HF 2 dB
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0
I also got a "communication error" when I tried to upload a new photo file. That I haven't seen before.
Photo fileUploading...
Communication error
Perhaps my debian has gotten corrupt somehow.
Right now I am trying a forced (normally unnecessary) "upgrade" from v1.661 to v1.661 to see if that fixes things. If not, I think I need to make a new debian 10.11 image (flash the card again) and scrap the old 10.11 one.
Update: The "communication error", photo problem fixed itself. Kiwi is online now with the correct config files and a new photo file, but the temppwd is still needed on ssh. For now I let it run as this.
jks,
Yesterday I was going to try and download an image again, and was having difficulty locating the correct image. In the past it would not upgrade from the 1.2 version, but you did mention that you fixed that, so I decided to give it a try. I let it sit overnight and the next day I discovered that it did upgrade by itself. it is now running 1.665, Debian 8.5.
Yes, there was a period of time after the Debian guys moved Debian 8 onto the "archive" repo servers that v1.2 got stuck trying to update. I thought all was lost until I figured out that /etc/apt/sources.list needed to be updated (the Kiwi Makefile now does this for D7/8/9). A lot of this stuff I don't understand very well..
Thank you for your help.
My KiwiSDR is on the fritz again. This time with a different problem. I wish I could hook up a monitor and keyboard and see what the problem is. I am frustrated. But I like the Kiwi alot. I am ready to purchase another one when there is new stock next month.
I tired this:
http://kiwisdr.local:8073/
I get the Chrome messsage:
This site can’t be reached Check if there is a typo in kiwisdr.local.
If spelling is correct, try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
I tried this:
http://my.kiwisdr.com/
I get the message:
No KiwiSDR(s) found for your public IP address: xxx.xxx.xxx.xxx
If necessary, temporarily disable any VPN or private relay service for this computer
(the one running the browser) so your actual public IP address can be found.
If enabled, a Kiwi registers itself on my.kiwisdr.com whenever it restarts.
My router does not see the Kiwi.
I get the blue cylon lights back and forth, and all also all blue lights blinking at the same time. Was thikning maybe it wa my power supply again. Tried another power supply, 5V 3A. Still didin't work. Tried doing a restore from my previous image backup. Didn't help either.
Could you email your public IP and/or serial number to support@kiwisdr.com please?
I can look on the server and see if it recorded any information as part of the my.kiwisdr.com registration.
My ISP changes my IP regularly, at least once a week.
I can email you my serial, and also what I believe was my last IP or one of my last IPs when my Kiwi was working.
Okay, please do. That way I can check for any evidence on my end of what your Kiwi might be doing.
Also, it might be useful if you could try decoding the pattern in the 4 blue LEDs to verify the local IP address. It's a painful process unfortunately. Documented here: http://kiwisdr.com/quickstart/index.html#id-leds
If there is ever a Kiwi-3 I'm going to use one of those little 1.9" OLED displays to show the IP address etc. in text form. A much better way to go.
Ok I will try to decode the pattern.
I have determined that the issue is with the new Linksys router I installed recently. I tried my old Linksys router again and the Kiwi works just fine. I am guessing it has something to do with the router using ipv6 to connect to all of my devices. Whereas my old router showed all the IPV4 addresses of my connected devices, my new router shows IPV6 addresses. It would have been ok with me since all my other devices connect just fine, just not the Kiwi. I was on chat with Linksys Customer Service for over an hour trying to get them to tell me how to force my router to use ipv4. I already found the tick mark for disabling ipv6 but that did not do anything. They are telling me to reset and reconfigure my router. The router doesn't even have a way to back up to a file. I'm going to turn off and on my router now. If that doesn't work I'm going to reset the router, and if that doesn't work I'm returning the router to Amazon.
Does KiwiSDR support IPv6?
Not fully.