FS#22011 - [kernel26] 2.6.36.1-3 hostap failure with RT2501/RT2573

Attached to Project: Arch Linux
Opened by Andre Kuehne (aku) - Tuesday, 07 December 2010, 18:30 GMT
Last edited by Tom Gundersen (tomegun) - Saturday, 18 June 2011, 19:41 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I use a USB WLAN Stick (model: TP-LINK TL-WN321G) with hostapd.
With kernel26-2.6.36.1-3-x86_64 this setup is not working anymore.
The interface is up and if I try to connect with another client WPA handshake also seems to work, but the IP configuration via DHCP fails.

After downgrading to kernel26-2.6.35.8-1-x86_64 the connection works fine again. I attach some basic information. Please let me know if you need any more specific feedback.

> lsusb
...
Bus 001 Device 003: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter
...

> lsmod
...
rt73usb 21779 0
rt2500usb 17334 0
rt2x00usb 7597 2 rt73usb,rt2500usb
rt2x00lib 25013 3 rt73usb,rt2500usb,rt2x00usb
mac80211 189270 2 rt2x00usb,rt2x00lib
cfg80211 144231 2 rt2x00lib,mac80211
...

> cat /etc/hostapd/hostapd.conf
...
interface=wlan0
bridge=br0
driver=nl80211
country_code=DE
ieee80211d=1
hw_mode=g
beacon_int=100
dtim_period=2
max_num_sta=255
rts_threshold=2347
fragm_threshold=2346
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
...

> grep hostap /var/log/messages.log
... authenticated
... associated (aid 1)
... RADIUS: starting accounting session 4CFD0763-000001A0
... WPA: pairwise key handshake completed (RSN)
...
This task depends upon

Closed by  Tom Gundersen (tomegun)
Saturday, 18 June 2011, 19:41 GMT
Reason for closing:  Upstream
Additional comments about closing:  Works with workaround.
Comment by JM (fijam) - Tuesday, 03 May 2011, 12:09 GMT
Is the bug still present in a current kernel version? Did you check if upstream is aware of it?
Comment by Andre Kuehne (aku) - Sunday, 15 May 2011, 13:39 GMT
I discussed this on IRC. Workaround seems to be "options rt73usb nohwcrypt=1". This is what i am currently doing. I posted details on the wireless mailing list, but they were already aware of this. Not sure if it already works again without nohwcrypt=1. I will try to find some time next week to test this.

Loading...