Closed adosikas closed 2 years ago
Just saw this and found that nmcli now needs installing separately. Verified this issue by connecting to the running container and found that nmcli wasn't installed at all.
Pushed 0.4.3 which has an updated Dockerfile to install networkmanager-cli
. Please try this and see if it fixes the issue.
That fixed it, thanks
I am getting the following behavior after updating system packages (running on a Pi3B+, supervised install):
On container restart, AP works fine for a couple minutes, then devices are unable to keep connections with
AP-STA-POSSIBLE-PSK-MISMATCH
in log.Manually running
sudo nmcli dev set wlan0 managed no
and restarting the container seems to work as workaround.Log from startup: