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#35056 - [netctl] wpa-config does not use correct wpa_supplicant.conf
Attached to Project:
Arch Linux
Opened by doak (doak) - Wednesday, 01 May 2013, 21:03 GMT
Last edited by Jouke Witteveen (jouke) - Thursday, 02 May 2013, 08:31 GMT
Opened by doak (doak) - Wednesday, 01 May 2013, 21:03 GMT
Last edited by Jouke Witteveen (jouke) - Thursday, 02 May 2013, 08:31 GMT
|
DetailsDescription:
Option 'Security=wpa-config' does not work as configured wpa_supplicant configuration file (option 'WPAConfigFile') seems to be ignored. Both can be configured in netctl profile. As a result the process 'wpa_supplicant' is started by 'netctl-auto@.service' using a some generated configuration missing every part of 'WPAConfigFile'. Therefore wifi can not associate to any (configured) access point. I attached a patch which works for me, but I am not sure if I did it right/as supposed. Additional info: * package version(s): v0.8-1 (semms not addressed in current version v1.0 as well) * config and/or log files etc: ** attached 'wireless-wpa-config * attached patch for '/usr/bin/netctl-auto' Steps to reproduce (as far as I know): 1) Packages 'netctl', 'wpa_supplicant' and 'wpa_actiond' has to be installed. 2) Create '/etc/netctl/wireless-wpa-config' (see attached file). 'wpa_supplicant.conf' should already be configured. 3) Stop any conflicting service. 4) 'sysctl start netctl-auto@<wifi-interface>.service' |
This task depends upon
Closed by Jouke Witteveen (jouke)
Thursday, 02 May 2013, 08:31 GMT
Reason for closing: Won't implement
Thursday, 02 May 2013, 08:31 GMT
Reason for closing: Won't implement
Comment by Jouke Witteveen (jouke) -
Thursday, 02 May 2013, 08:30 GMT
You need to extract the network block from the file if you want to use it in netctl-auto correctly. If the configuration file allows this, you could as well write the network block directly into the netctl profile. In netctl.profile(5), it is stated that profiles with Security=wpa-config are excluded from automatic profile selection.
wireless-wpa-config