You are not logged in.
I recently started using wpa_supplicant to connect to the internet after formerly using netctl.
I am able to connect manually to my wl network, but I have to do it manually (as printed below from the wiki):
# wpa_supplicant -B -i interface -c /etc/wpa_supplicant/example.conf
# dhcpcd interfaceI tried automatically connecting using the following code:
# systemctl enable dhcpcd.service
# systemctl start dhcpcd.service
# systemctl enable wpa_supplicant@interface.service
# systemctl start wpa_supplicant@interface.serviceYet when I reboot, I have to reconnect manually. I am not sure what is going on because my technical skills aren't up to speed yet. I think it could be related to netct, which I uninstalled. Or I'm missing something.
A notable troubleshooting output:
systemctl --failedShows that for the relevant interface, LOAD == 'loaded', ACTIVE & SUB == "failed".
Note: I am not able to share full outputs, I can only type them out.
Last edited by prayner96 (2022-04-24 22:37:43)
Offline
And did you edit the wpa_supplicant service file to use "example.conf" instead of the default wpa_supplicant.conf? Why are you even using "example.conf'? (edit: I see this is now in the wiki ... so that explains where it came from - but it really shouldn't be in the wiki like that)
On another note, I'd not boter with the wpa_supplicant service, use the dhcpcd hook instead:
https://wiki.archlinux.org/title/Dhcpcd … supplicant
Last edited by Trilby (2022-04-24 14:34:33)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Hi Trilby, thanks for getting back to me. Yes example.conf in this case would be wpa_supplicant.conf, I just copy-pasted it from the wiki. I will give your approach a try in a few hours (time to vote!)
Offline
Solved. Thanks for your help!
The output for systemctl --failed is still the same though. Not sure if that matters in the long run.
Offline