Possible DNS issue with one of two Kiwis on same network
Totally at loss here, maybe a no-ip DNS issue but Im raising the issue here. I have two Kiwis set up to a fiber connection yesterday. I set up address/mac binding, virtual servers ok on a tp-link router. Everything in both kiwis are identical apart from name and port no. they are arcticsdr.ddns.net:8073, and kongsdr.ddns.net:8074. I had an old account with no-ip which was reactivated. For at least 48 hours everything worked well, then I got message that kongsdr was unaccessible. I checked at no-ip and found that the IP/Target was wrong: the correct public ip is the one associated with arcticsdr (see attachment) I corrected this, but after refresh the wrong IP (77-etc) returned. There is a short period (seconds maybe) when external connection is ok after actions like rebooting Beagle, and after I changed IP in no-ip, and after I deleted kongsdr from no-ip, and added it anew. No-ip tests show that ports are open, but check port open in Kiwi Network returns NO and YES. So, according to the Kiwi GUI: If first responds "NO" and second "YES" then domain name of the first isn't resolving to the ip address of the second. Check DNS.. Public IP has not changed since the Kiwis were put online.
The strange thing is that occasionally, often after reloading several times, external connection is made. Those who have actually logged in, are not affected by any action I make, except of course the Beagle reboot. The other Kiwi, arcticdsdr has no issues at all. So far!
Maybe I have to go back to proxy.
Attachments:
https://forum.kiwisdr.com/uploads/Uploader/e7/711adcd639a38a8e79cd24fec4f98a.jpg
The strange thing is that occasionally, often after reloading several times, external connection is made. Those who have actually logged in, are not affected by any action I make, except of course the Beagle reboot. The other Kiwi, arcticdsdr has no issues at all. So far!
Maybe I have to go back to proxy.
Attachments:
https://forum.kiwisdr.com/uploads/Uploader/e7/711adcd639a38a8e79cd24fec4f98a.jpg
Comments
Or even more out-there a "Total Kiwi", and "this kiwi number" so 1of4 sends at different times to 2of4 3of4 etc.
Only other thing I can think of quickly is some network buffer that is caching your request. so you send the update, it fails due to timing or network load/conflict, the ISP server at "wrong address" resends?
--oh and why do you need two DUC addresses anyway if they are at the same IP?"--
I didn't quite grasp the intention behind the last sentence - take into consideration I am quite uncomfortable with networking, that kind of anyway ;-)
I first disabled the Kiwi built-in DUC client on both Arctic and Kong and made sure there was no DUC process running on the Kiwis.
Then I went to noip and manually set the target ip to 213.161 ... (via the "modify" button) for both Arctic and Kong and observed that the "last update" time shown on that page (the last time noip received an update request from any DUC client with the proper credentials) was 21:00 CET.
So far, so good.
But at 21:19 someone sent an update to noip for Kong with an ip of 77.222 ... The 21:00 update for Arctic remained from before.
So the issue is who is doing this? A check of the Kiwis again showed no DUC clients running.
Did you ever download from noip a DUC client to run on a Windows or Linux box that might still be running with the 77.222 address configured?
Related have you considered changing the password for no-ip? If another user / piece of hardware tries to update that address it should fail if it has the wrong password...
Ghost DUC, haunted Kiwi obviously....
"Thank you for information. After noting that behavior and pulling further logs, it appears as if the hostname is receiving updates from two sources. It's either there are multiple DUCs on one network, or the network device has the hostname kongsdr.ddns.net configured within it.
No-IP is receiving the dynamic updates for the hostname and resolving it appropriately to the supplied IP as shown by the attached logs. Sometimes our ticketing system has issues with attachments, so if what I've sent doesn't make it, I can send it separately.
Take a look at your network configurations and let me know if you have any further questions or concerns."
Edit: I didn't notice John's question: The DUC I downloaded from no-ip only shows 213.etc. If I refresh the NUC, the Target/IP goes back to 213.. but then changes back to 77...
Attachments:
https://forum.kiwisdr.com/uploads/Uploader/a8/91352757914092b1b5a500fe34a9f2.txt
I would say create a new account on noip and remove your old one to try and shut-out the ghost DUC. You can't just change the account password because if the ghost DUC is persistently connected it may not get booted just because the password changed. Also, before you do this, leave the DUC on both Kiwis disabled and don't enter the new account info at first. Configure the public ip for Arctic and Kong using the web interface at noip and see if it stays good for a while. Then enable the DUC on one of the Kiwis and see if the ip stays good.
It is possible...