|
Edited by Bazmundi at 2018-9-2 16:45
So I set the update to a fixed time interval (1am to 2am in the morning). Set up the board with only Ubuntu Core running. I went off to potter at another task. Came back and OPiZ had dropped off the network.
That is, with a brand new Ubuntu Core image, with nothing else running, no snaps installed (other than the core), no configuration changes, the board will drop off the network.
It doesn't appear to be a dynamic IP re-assignement. The same fixed IP address keeps reporting on the OPiZ serial console even while the OPiZ cannot be seen on network.
The admin page of my wifi extended reports the IP address for the OPiZ for a short time. Then it drops off the device list. There is no other device that comes up in its place (typical of a dynamic IP reassignment). That is the device list on my router is n long when OPiZ is running and n-1 when it is not.
I had seen this behaviour, not so bad, with other images including Arbian and the official Debian server for OPiZ. I have suspicions it is in the design of the OPiZ hardware since it occurs over a number of raw linux installs. That is, with a fresh SD card and minimal config changes the behaviour occurs. Note that it also occurs when static IP has been set (on both Arbian and official Debian server versions).
I am going to bomb another SD card with a Ubuntu Core image for Raspberry Pi I have to see if the Raspberry Pi does the same thing.
<UPDATE>
GAG! Sorry, can't try the Ubuntu Core on RPi 3B+ yet as there is no image for that model.
</UPDATE>
Cheers,
A
|
|