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#30583 - [wpa_supplicant] upgrade to 1.0-1 breaks WPA2 authentication
Attached to Project:
Arch Linux
Opened by Stefan Förster (HotblackDesiato) - Saturday, 07 July 2012, 10:01 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 12 February 2014, 01:55 GMT
Opened by Stefan Förster (HotblackDesiato) - Saturday, 07 July 2012, 10:01 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 12 February 2014, 01:55 GMT
|
DetailsDescription:
A few days ago I updated two of my notebooks running Arch Linux. One of the updates was wpa_supplicant, from version 0.7.3-5 to 1.0-1. The result was that I could no longer connect to my access point, even in the near vicinity with about 85% signal strength. I could single out a router problem or other external causes, since my son was still able to connect to this access point with his Nintendo DS and his Huawei MediaPad. I donwgraded wpa_supplicant back to version 0.7.3-5 and both notebooks connected immediately to the router. Thus wpa_supplicant 1.0-1 is buggy. On both notebooks I use wicd to connect to the internet. With version 1.0-1 of wpa_supplicant installed, wicd tries to connect to the access point several times for several minutes and finally displays "BAD PASSWORD", which is wrong, since there has been no change to settings (notebooks & router) and I checked that the password is correct. notebook #1: IBM ThinkPad X41 with an Intel wifi interface (driver: ipw2200). KDE & wicd notebook #2: IBM ThinkPad T23, SMC PCMCIA wifi card, prism chipset (driver: p54pci). fluxbox & wicd Steps to reproduce: 1. install wpa_supplicant 1.0-1 and wicd 2. try to associate to an access point with WPA2 encryption |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Wednesday, 12 February 2014, 01:55 GMT
Reason for closing: Works for me
Additional comments about closing: Bug can not be replicated to test.
Wednesday, 12 February 2014, 01:55 GMT
Reason for closing: Works for me
Additional comments about closing: Bug can not be replicated to test.
Could this be related: http://ubuntuforums.org/showthread.php?t=1675398 ? I realise they talk about much older versions, but it seems the problem is the same.
I don't know whether this is related to last year's discussion in the ubuntu forums. Last year, wicd (and also networkmanager, which I had also tried) had always worked for me under Arch Linux.
The "BAD PASSWORD" message by wicd is definitely a lie, in fact, there is no way to know why a connection failed (I have other devices that always say "out of range" whenever connection fails).
A logfile from wpa_supplicant with -d or -dd option may help determine what's wrong here. Details on your network might also be useful, as displayed by 'wpa_cli scan_results' or the more detailed output of 'iw dev wlan0 scan dump'.
On my notebook when using network-manager, I get a connection with wpa_supplicant 0.7.3-5, but not with 1.0-1. Thus I can confirm that this behaviour is not wicd specific also for my notebook, not only for my wife's notebook.
I also tried wpa_gui, which doesn't work (shows now device at all !?), but ifconfig clearly shows wlan0.
Can you give me a hint how to manually start wpa_supplicant?
I did the following:
1) I killed the nm-applet task
2) /etc/rc.d/network-manager stop
3) wpa_supplicant -dd -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
I know that "wext" is correct, since wicd uses this setting. My wpa_supplicant.conf is just simple:
------------------
ctrl_interface=/var/run/wpa_supplicant
update_config=1
network={
ssid="Linux"
proto=WPA
key_mgmt=WPA-PSK
psk="?????????????????"
group=TKIP
}
-----------------
The network block should be minimal, you provide too many options:
network={
ssid="..."
proto=RSN WPA
psk="..."
}
The proto=RSN WPA prefers WPA2 over WPA, but it isn't very important. proto=WPA limits to WPA only.
Anyway, after the upgrade to libnl 0.21, wpa_supplicant needed to be updated because the name of the libnl shared library changed.
I downgraded both libnl and wpa_supplicant and they worked again, then I reinstalled the new versions and checked if they were working, but they were not.
After some testing I've decided to recompile the packages (don't ask me why, I had no ideia what else to do), and to my surprise they worked again!
I've noticed the connection was losing a lot of packets, but it was working so I didn't care about that.
But, yesterday, after an upgrade, it stoped working again. I checked the packages that were upgraded and to my surprise nor libnl nor wpa_supplicant were updated, but I've noticed the kernel was, so I started to wonder... maybe it's a driver issue? Any clues?