% sudo netcfg -r wlana :: wlana down [ DONE ] :: wlana up [ BUSY ] Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory ^C% % sudo netcfg -r wlana > Profile not connected :: wlana up [ DONE ]
... repeatedly while netcfg seems to hang in that loop, but only on every second reconnect (Meaning when the connection is already up; Initial connection works. Starting at the first "netcfg -r" I get the message. Hitting strg+c and starting it a third time means it works again... and so on). Other than that, all of netcfg / wifi works just fine. I experience none of the problems that are (according to archwiki + google) usually connected to this error message.
Using the standard wpa_supplicant.conf. Manual connection works fine... only one instance of wpa_supplicant is running while netcfg is working. No instance at all is running, while it's spamming the error / failing to reconnect.
Last edited by whoops (2013-05-04 07:24:28)
I have the same problem,
I created /etc/wpa_supplicant.conf
ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel fast_reauth=1 ap_scan=0
I also append this in /etc/conf.d/netcfg
but without luck
so I'm tired of running netcfg -r profile two times ((
I've seen this in many posts - I've never used netcfg, but it seems it doesn't actually check whether wpa_supplicant or dhcpcd are running before it tries to restart them. This leads to many errors as they cannot be restarted until the previous instance is shut down. I'd report this upstream as a bug, it is ridiculous for it not to check and shutdown previous instances ... and it is simple for it to do so.
EDIT: solution: don't use netcfg.
Last edited by Trilby (2013-01-10 12:53:35)
This seems to have fixed itself. Don't know why, but it might have had something to do with other devices on the network that were trying to force to router to use different wifi settings / speed.
Last edited by whoops (2013-05-04 07:26:27)