Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39513 - [wpa_supplicant] /usr/lib/systemd/system/wpa_supplicant@.service kinda useless without a dhcp client
Attached to Project:
Arch Linux
Opened by Kai Hendry (hendry) - Tuesday, 18 March 2014, 03:32 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Tuesday, 18 March 2014, 11:14 GMT
Opened by Kai Hendry (hendry) - Tuesday, 18 March 2014, 03:32 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Tuesday, 18 March 2014, 11:14 GMT
|
DetailsDescription:
I noticed /usr/lib/systemd/system/wpa_supplicant@.service from https://bbs.archlinux.org/viewtopic.php?pid=1393494#p1393494 It makes the wireless interface correctly associate with the ESSID, but where is the IP address? After enabling dhcpcd@wlan0.service, my wireless network interface is up and running... BUT dhcpcd@wlan0.service invokes wpa_supplicant from /usr/lib/dhcpcd/dhcpcd-hooks/10-wpa_supplicant, so there is no need for wpa_supplicant@.service AFAICT? I'm maintaining a blog post about how to setup a network connection on my X220 http://dabase.com/blog/Good_riddance_netctl/ between wpa_supplican and dhcpcd packaging ... Additional info: * 2.1-3 Steps to reproduce: sudo systemctl enable wpa_supplicant@wlan0.service sudo systemctl enable dhcpcd@wlan0.service |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Tuesday, 18 March 2014, 11:14 GMT
Reason for closing: Not a bug
Tuesday, 18 March 2014, 11:14 GMT
Reason for closing: Not a bug