Andrei Borzenkov wrote:
On 02.03.2021 11:52, Per Jessen wrote:
On a small ARM board running openSUSE Leap, I need to configure the Wifi interface, after the first boot-up from the jeos image (which will include my code). The user can only interfact with the ARM board via the tiny 160x80 LCD screen and a numeric keypad. So I need to write some code to interface the latter two with <something> to configure the wifi. The interfacing is not difficult, but once I have the information (ESSID and password), the question is - how do I configure the wlan0 interface (for dhcp) ?
Using whatever network management framework you have. All that wpa_supplicant does is "plugging in cable". What happens after interface link is up is entirely out of scope of wpa_supplicant.
You were actually asking the wrong question....
I had been out googling and seen how people on Raspberry Pis was doing it, and they seemed to default to fiddling with wpa_supplicant. I guess I was misled ....
I have amended my wpa_supplicant config, adding '-i wlan0' to the start-up. So far so good - I have also used wpa_passphrase to generate the network config in wpa_supplicant.conf, but after a restart I am only getting some IPv6 addresses, but no IPv4 - I'm guessing I need to figure out how wpa_supplicant interacts with wicked ??
Wicked interacts with wpa_supplicant over D-Bus so you do not need to do anything with wpa_supplicant at all - just configure wireless interface in wicked as usual. E.g. by directly dropping ifcfg-wlan0 in /etc/sysconfig/network.
As I normally would :-) One of my objectives is to remain "compatible" (as much as possible) with the way it is done in openSUSE - I'm happy with editing ifcfg-wlan0. -- Per Jessen, Zürich (6.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.