David C. Rankin wrote:
On 3/1/21 6:33 PM, David C. Rankin wrote:
(but you will need to find out what state directory wpa_supplicant was compiled to use instead of the old /var/run)
You can probably just look at the .spec file if nobody here knows off-hand.
I think the location is fine - /var/run/ is symlinked to /run.
From an overview standpoint, wpa_supplicant is just the tool that associates ESSID and a password with an interface and then facilitates the authentication to that interface when used.
Right, that sounds like what I need. My user interface has to enable the user to configure the wifi - ESSID, authentication, password.
To use wpa_supplicant in the past, all I did was to run wpa_passphrase to setup the config for the inteface, e.g.
wpa_passphrase "your_ESSID" "PassPhrase_up-to-64-Characters" \ >> /etc/wpa_supplicant.conf
That will save the ESSID/passphrase in wpa_suppliment.conf
Then to activate the interface, you use something similar to the following (but you will need to find out what state directory wpa_supplicant was compiled to use instead of the old /var/run) and do:
wpa_supplicant -iwlan0 \ -c/var/run/wpa_supplicant-ath0.conf \ -Dwext \ -P/var/run/wpa_supplicant/ath0.pid \ -B
wpa_supplicant appears to be running by default, so I guess I need to look at how to provide an interface name, via d-bus as Andrei mentioned. -- Per Jessen, Zürich (1.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.