Not fixed yet but also they removed the “Edit” option from long press on a wifi access point name, in Settings → Wifi, after ~4.3v SFos (Please Jollaboys bring it back!). From my experience so far: It is random. My DHCP server (the internet provider’s router I have) some times does not work as it should and doesn’t respect the IP range I have set, no ideas if it has anything to do. Some times IP is lost but IPv6 DNS appear even I have only IPv4 settings.
A workaround that I will test the following days:
From command as root line you can see the WiFi that are saved in connmann with the following command:
connmanctl services
It should appear a list, the second row is the AccessPoint (A/P) name and the third the unique name connmann uses for the specific A/P, ex" wifi_1b123456c12f_123c123c3a7b6e_managed_psk (The following part is only informational: this is also the name of a folder you can find in: /home/defaultuser/.local/share/system/privileged/connman . In there you will find a “settings” file that has all the info of the specific wifi A/P (Name, Passphrase, IP etc) ).
Using connmanctl you can connect to a specific wifi:
connmanctl connect wifi_1b123456c12f_123c123c3a7b6e_managed_psk
and also set some parameters:
connmanctl config wifi_1b123456c12f_123c123c3a7b6e_managed_psk --ipv4 manual 192.168.0.10 255.255.255.0 192.168.0.1 --nameservers 192.168.0.1 192.168.0.2 --ipv6 off
I will make a shell script and run them as root every time I have the problem.
A second lazy workaround I do is to go to wifi Details, Edit → check Auto-retrieve IP address → Save, Edit again, uncheck Auto-retrieve IP address, and I see the fields filled from DHCP. I usually edit only the last number of the IP and I am okey.
I also tried to chmod 400 (readonly by root) the settings connman file, but the moment I run the above connman command to change the settings the file got writen and appeared with chmod 600 (read-write).
Cheers
