I simply do:
systemctl start wpa_supplicant
No errors --- I get a new prompt. Ok, so far, so good.
I check journalctl.
wpa_supplicant: Successfully initialized wpa_supplicant
Nothing more, again, so far, so good.
But then, of course, when I check
ps aux | grep wpa, I get nothing at all.
So, not only does
systemctl fail to start it, fail to inform it wasn't started, but there is nothing in
journalctl about any problem at all. Just that it was "successfully initialized".
If I manually start
wpa_supplicant, e.g. with this:
wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlan0
Then it starts up perfectly fine, and even successfully authenticates with the AP in the
Apparently, I have no idea how to use systemd. But when I get no errors, warning, or even information, it is not exactly intuitive to me what the problem is, but then again, I'm not used to using systemd. I can imagine others would encounter the same or similar problems trying to use systemd, and become just as frustrated as I am.
This is for Kali Linux Rolling. 4.13.0-kali1-amd64, systemd 235, wpa_supplicant v2.4.
systemctl status wpa_supplicant ● wpa_supplicant.service - WPA supplicant Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; enabled; vendor preset: disabled) Active: inactive (dead) since Sat 2017-12-30 22:57:47 CET; 1min 0s ago Process: 1267 ExecStart=/sbin/wpa_supplicant -B -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlan0 (code=exited, st Main PID: 1267 (code=exited, status=0/SUCCESS) Dec 30 22:57:46 w530 systemd: Starting WPA supplicant... Dec 30 22:57:46 w530 wpa_supplicant: Successfully initialized wpa_supplicant Dec 30 22:57:47 w530 systemd: Started WPA supplicant.