wpa_supplicant authentication may have failed, wicd with wpa2wpa_supplicant authentication may have failed, wicd with wpa2 fails

source : debian-user-digest # 1174,1175,1176,1183.

[ A ] : try removing network-manager.

[ B ] : Try starting "wp_supplicant" in debug mode to make the log more verbose about that error. It seems failing at some point of the authentication.
Also, try to lower the security a bit by choosing WPA-PSK ( TKIP ) or WPA2-PSK ( AES+TKIP ) instead just AES. Stronger encryption requires better coberture so devices can "dialogue" smoothly.

[ C ] : It might be better to put away wicd for a moment and invoke wpa_supplicant directly with the -d switch. You may have to set the ssid first with iwconfig(8).

[ D ] : Reviwer your "/etc/dbus-1/system.d/wpa_supplicant.conf" or whatever the config file is. AP and wpa_supplicant settings must match.

[ E ] : One thing I've done a few times, that may help here, is to create a temporary wrapper script to run some command.

That is, go to the executable file location, rename it, say xx.orig, and create a short script named xx, that will start the xx.orig with the debug options you want. You probably want to use as the last arg the form "$@" ( include the quotes ), which will supply any arguments from the script to the real program exactly as they were given to the script.

In case there's some std* output from the original that doesn't get written to a log file, you can add this at the top of the script, to capture that output in your own log file :
exec >/tmp/xx.orig.$$.log 2>&1

Or just put everything after the 'exec' above, after the xx.orig command line. The advantage of using the 'exec' form is that any output the script generates for any problem will also be written to the file ( syntax errors, other commands failing, etc ).
 
 

This work by maniac.vardhan is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.