Description of problem: Connecting to WPA2 (probably WPA as well) wireless requires specifying the type (TKIP), at least on an Acer Aspire 3002CLi. If it's set to automatic, it fails. If set to AES, it fails (perhaps the card cannot handle AES, but automatic should figure that out!). If set to TKIP, it will work. The router was set for WPA2 Personal, both AES & TKIP, and the card only connected if I specified TKIP. Version-Release number of selected component (if applicable): 0.6.4-7.el5 How reproducible: Always Steps to Reproduce: 1. Obtain a Acer Aspire 3002CLi 2. Attempt to connect to a WPA2 wireless network via Default (automatic) Actual results: It will fail, unless you specify TKIP Expected results: Should figure it out! Additional info: Not a regression. My home AP: Lynksys WRT54GL One of the QE testing laptops' internal cards, BCM4318
any chance I can get access to both the laptop and the AP to debug the issue directly?
Laptop, yes. AP... not easily, as I am not the only one using it. I shall check if I can reproduce an an AP in the office next week, and if not talk to my roommate to see when I can bring it in.
This is also reproducable with QE's in-house router, so I can provide both laptop & AP. Are you at work today?
Yeah, bring them by or I can come find you.
Need to reverify with 5.3 though it should be fixed with kernel driver updates to bcm43xx as well as the NM rebase.
We shall assume this is fixed.