I finally sat down and did some searching... The DNS was a mess with the first line looking at 192.168.0.1, it apparently never would skip to the next line of 8.8.8.8. This is why it couldn't update. the fix is from their github issues (because a forum is beyond their capacity?):
Hello, The changelog for version 2.1.6 lists the following change perf: removed unnecessary modifications to DNS configuration I understand it is in relation to this answer where you stated you wou...
github.com
Edit this to set your preferred/required DNS servers, and it will finally get out. I'm not sure why they didn't just use the DNS provided from your DHCP server, the IP is handled by DHCP so the DNS really should have been handled this way too.
You may also need to turn on the "preview updates" to get the latest thing (currently version 2.2.6), not sure what it changed, still no http/https upload for images to the card, still no manual IP and DNS entry areas. But at least they are still working on it.
Uploading images at about 4-5 MBps over SCP (turn SSH on first).
In the 1.4.0 system image, it does default to forcing you to update the admin password before you can do anything, so at least that is better.
I need to see if I can configure my last lab machine to wake on LAN so I can give this a full test, then use it to install an OS and then control that OS. I'm not certain I will leave this connected when not in use, I still want to sniff the network and see what I can see with this latest application (v 2.2.6).
[edit] Looked at my firewall, and the only thing I don't like is this:
Code:
Apr 25, 2025 1:36 PM
Apr 25, 2025 1:38 PM
Device (48da356f1937) Others 172.30.1.9 39008 stun.l.google.com 19302 Conferencing Google Meet
Not sure if it is really google meet, or just another google connection, going to have to find out as this thing does not need to be generating/joining a meeting!