wpa_supplicant randomly stopped working.

It was trouble enough to get it working in the first place...

I turned on my computer today and ath0 wasn't doing it's job.

Quote:

---

* Starting ath0
* Starting wpa_supplicant on ath0 ... [ ok ]
* timed out ... [ !! ]

---

I shut off the encryption on my router and tried connecting without wpa_supplicant and it worked.

so i tried re-emerging madwifi-ng wpa_supplicant dhcp* and while emerging it gave me an error message:

Quote:

---

/usr/portage/profiles/default-linux/profile.bashrc: line 70: has: command not found.

---

what is "has" and why don't I have it anymore??

I did "emerge -uD world" recently and it did update bash... maybe systools or something...

I'm all out of ideas... please help.

Anyone? Any brainstorming would be really helpfull.

did you run env-update after the emerge world?

thanks for the reply.

I didn't run env-update, but I thought portage ran it after every package merge. I ran it and it didn't change anything.

I tried running net.ath0 with NET_DEBUG set and it looks like the script isn't recieving a signal from wpa_supplicant or something. This is the output right after it executes wpa_supplicant :

Quote:

---

+ (( i > 0 ))
+ (( i = RC_DEFAULT_INDENT ))
+ esetdent 4
+ local i=4
+ (( i < 0 ))
++ printf %4s ''
+ RC_INDENTATION=' '
+ veinfo 'Waiting for association'
+ [[ no != yes ]]
+ eend 0
+ local retval=0
+ shift
+ _eend 0 eerror ''
+ local retval=0 efunc=eerror msg
+ shift 2
+ [[ 0 == 0 ]]
+ [[ no == yes ]]
+ msg='[ ok ]'
+ [[ yes == yes ]]
+ echo -e ' [ ok ]'
[ ok ]
+ return 0
+ LAST_E_CMD=eend
+ return 0
+ wpa_supplicant_associate ath0
++ interface_variable ath0
++ LC_ALL=C
++ echo ath0
+ local iface=ath0 ifvar=ath0 timeout i
+ eval 'timeout="${wpa_timeout_ath0:-60}"'
++ timeout=60
+ (( i=0 ))
+ (( i<60 ))
+ wpa_supplicant_associated ath0
+ local -a status
++ wpa_cli -iath0 status
++ LC_ALL=C
++ /bin/wpa_cli -iath0 status
++ awk -F= '/^key_mgmt|^wpa_state|^EAP state/ { print "\""$2"\"" }'
+ eval 'status=("DISCONNECTED")'
++ status=("DISCONNECTED")
+ case ${status[0]} in
+ [[ '' == \C\O\M\P\L\E\T\E\D ]]
+ return 1
+ sleep 1
+ (( i++ ))
+ (( i<60 ))
+ wpa_supplicant_associated ath0
+ local -a status
++ wpa_cli -iath0 status
++ LC_ALL=C
++ /bin/wpa_cli -iath0 status
++ awk -F= '/^key_mgmt|^wpa_state|^EAP state/ { print "\""$2"\"" }'
+ eval 'status=("UNKNOWN"' '"ASSOCIATED")'
++ status=("UNKNOWN" "ASSOCIATED")
+ case ${status[0]} in
+ [[ ASSOCIATED == \C\O\M\P\L\E\T\E\D ]]
+ return 1
+ sleep 1
+ (( i++ ))
+ (( i<60 ))
+ wpa_supplicant_associated ath0
+ local -a status
++ wpa_cli -iath0 status
++ LC_ALL=C
++ /bin/wpa_cli -iath0 status
++ awk -F= '/^key_mgmt|^wpa_state|^EAP state/ { print "\""$2"\"" }'
+ eval 'status=("WPA-PSK"' '"ASSOCIATED")'
++ status=("WPA-PSK" "ASSOCIATED")
+ case ${status[0]} in
+ [[ ASSOCIATED == \C\O\M\P\L\E\T\E\D ]]
+ return 1

---

It looks like it's the ASSOCIATED part. the script wants a COMPLETED signal or something... what does associated mean?

SOLVED

luckely I stumbled upon this bug: #130104

apparently wpa_supplicant isn't working nicely with bash 3.1
The patch didn't work for me so I re-emerged bash 3.0.

this is a list of packages I have installed in case anyone else has this problem.

Quote:

---

sys-apps/baselayout-1.11.14-r7
app-shells/bash-3.0-r12
sys-libs/readline-5.1_p2
net-wireless/wpa_supplicant-0.5.2
net-wireless/madwifi-ng-0.1473.20060312
net-wireless/madwifi-ng-tools-0.1473.20060312

---