August-30th-2018, 01:30 PM
Well setting a different IP address on Wifi Access point is obligatory, else you get a mismatch anyway.
So you say you didn't change anything in your LAN setting, so then it is running as DHCP client still waiting to receive an IP address from your DHCP server, right? ... because this is the default setting.
What you can do is connecting monitor to the HDMI port of netPI maybe giving you a log output about a misconfiguration.
But independent of what I have heard now, I have doubts that you get your netPI recovered without loading a new image to it. If there is no contact via no interfaces then all the contact to the system is gone.
Have you made a copy of your container, on Docker Hub for example with a free account? In this case it is no problem. It is just setting the LAN params again and reloading the container.
Regards
Armin
So you say you didn't change anything in your LAN setting, so then it is running as DHCP client still waiting to receive an IP address from your DHCP server, right? ... because this is the default setting.
What you can do is connecting monitor to the HDMI port of netPI maybe giving you a log output about a misconfiguration.
But independent of what I have heard now, I have doubts that you get your netPI recovered without loading a new image to it. If there is no contact via no interfaces then all the contact to the system is gone.
Have you made a copy of your container, on Docker Hub for example with a free account? In this case it is no problem. It is just setting the LAN params again and reloading the container.
Regards
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
