You are not logged in.
Recently wpa_supplicant was upgraded to version 2.0-1. After a reboot it couldn't connect to my wifi.
I couldn't see what the problem was, so I re-installed version 1.0-2 and it works fine.
Now I have to hold back on an update to libnl because wpa_supplicant needs libnl.so-200, and the current is so-201.
I'm using the rtl8192cu module and wpa_supplicant-nl80211@wlan0.service
/etc/wpa_supplicant/wpa_supplicant.conf:
country=DK
ctrl_interface=/run/wpa_supplicant
network={
proto=WPA
priority=1
scan_ssid=1
ssid="myssid"
psk=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
mode=0
}
Do I need to change something to make it work with wpa_supplicant-2.0-2 ?
Last edited by Leo Laursen (2013-06-06 09:42:03)
Offline
Just to make sure, have you tried using wpa_supplicant 2.0 manually?
I laugh, yet the joke is on me
Offline
nagual# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
----
wlan0: Trying to associate with 00:24:8c:31:74:66 (SSID='C9v7xH3s' freq=2462 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlan0: Association request to the driver failed
wlan0: Associated with 00:24:8c:31:74:66
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:24:8c:31:74:66 reason=0
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="C9v7xH3s" auth_failures=1 duration=10
wlan0: CTRL-EVENT-SSID-REENABLED id=0 ssid="C9v7xH3s"
wlan0: Trying to associate with 00:24:8c:31:74:66 (SSID='C9v7xH3s' freq=2462 MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
wlan0: Association request to the driver failed
wlan0: Associated with 00:24:8c:31:74:66
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:24:8c:31:74:66 reason=0
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="C9v7xH3s" auth_failures=2 duration=20
^Cwlan0: CTRL-EVENT-TERMINATING
One of the changes is in the 4-Way Handshake. The psk is unchanged. I even tried to generate it with the new version of wpa_passphrase, which didn't change anything.
Offline
Hi Leo,
could you try the driver flag -Dnl80211 - i hope this will give a known reason code, look here for reference:
http://lists.shmoo.com/pipermail/hostap … 21816.html Reason=0 means "no information given", or really that the driver didn't pass up enough information for the supplicant to give you a reason code. Looks like only the nl80211 driver actually has the *capability* to provide reason codes,
reason code meaning: http://lists.shmoo.com/pipermail/hostap … 13218.html
edit:/ oooh and even try -dd flag for more verbose output and upload to some nopaste service.
Last edited by debijan (2013-03-03 09:48:45)
Offline
Hi Leo Laursen,
did you get some new results or a solution?
Offline
Hi debijan
I just did a quick update, and tried with flag -Dnl80211.
The results seems almost identical. The different lines are:
wlan0: SME: Trying to authenticate with 00:24:8c:31:74:66 (SSID='C9v7xH3s' freq=2462 MHz)
---
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:24:8c:31:74:66 reason=15
What is "reason 15"? The list you gave a link to only have reasons 0 - 9.
When I have time, I'll try with debug, and post a link.
Offline
When I have time, I'll try with debug, and post a link.
Log here, on DropBox: wpa.log.
What are the alternatives, if I want the wlan connection initialized on upstart?
Offline
I updated wpa_supplicant today, because of the /usr/bin move. I don't know why, but this time it worked. I've tried numerous times without success in the last three months.
Offline
Please use [Solved] rather than closed; the mods use that to denote a locked thread...
Offline