jks

Thanks for pointing out that Chuck is running RaspPIs (I checked, he has one that is public and no KiwiSDRs).

So Chuck is no longer with us. He can use the RaspPi forum for his questions.

Anything new about this? Could it be related to the Comcast/Xfinity problem others have had recently?

Yes, question is too short to understand exactly what is being talked about.

But to me it sounds like it's the local (private) ip address that the router is moving around for some reason. E.g. you y initialldiscover it's 192.168.1.101 and make a connection. But then later after trying to reconnect there is no response at that address and you have to go through the rediscovery process again only to find it's now at 192.168.1.107.

This might be caused by the DHCP server in the router configured with a really short "lease time", like minute or hours instead of days or weeks. Ideally the Kiwi's Ethernet MAC address should be bound to a fixed private ip address in the DHCP static ip configuration table. But that takes some effort to setup (that's what I do here). That way the local ip addresses never move.

Make sure this is not the problem before you send him off on the goose chase that is DDNS, lol.

@KB8DOA This morning (19 Jan 2021) R&S shows 13 Kiwi kits in stock. Please get on them immediately and make sure your two backordered units from last July get shipped so this awful situation can finally be resolved.

My sincere apologies for this situation. I never got any answers from anyone, including Seeed, about what happened exactly. I have guesses, but that's all. There is simply no excuse for it.

The forum server is located in the same datacenter as the one serving kiwisdr.com (California). Doing a traceroute on both ip addresses might tell you something.