On Mon, 2013-01-21 at 08:42 +0000, Ketan Kamat wrote: > Hi Luciano, > > I applied some of the code commits that were done to wl12xx driver (http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=history;f=drivers/net/wireless;hb=HEAD;pg=20 ): > > 2012-04-10 Eyal Shapira wl12xx: increase scan timeout to 30s > 2012-04-10 Eyal Shapira wl12xx: adaptive sched scan dwell times > 2012-04-10 Eyal Shapira wl12xx: fix a memory leak of probereq template upon > 2012-04-10 Eliad Peller wl12xx: free ap keys only in ap mode > 2012-04-10 Eyal Shapira wl12xx: fix race between suspend/resume and recovery > 2012-04-10 Victor Goldenshtein wl12xx: fix station channel switch > 2012-04-10 Eliad Peller wl12xx: set do_join on BSS_CHANGED_ASSOC > > After applying these changes, it got connected to WPA2-personal. Currently doing some more testing This sounds quiet weird. I don't think any of the patches you applied have any influence in AES connections. Are you sure you didn't change anything else? I just tried vanilla 3.4 and I didn't have problems connecting from my wl127x chip to a wl18xx running hostapd with WPA2/AES. -- Cheers, Luca. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
