Description of problem: When trying to connect my MacBook 2.1 to a hidden wireless wpa2 secured linksys wpa54g network this will not work. Version-Release number of selected component (if applicable): Latest rawhide kernel 2.6.29-68.fc11.i586 How reproducible: Everytime Steps to Reproduce: 1. Setup your WPA54G using WPA2 with hidden BSSID 2. Use a rawhide kernel 3. Use NM to setup the network Actual results: Connection can not be established Expected results: Secure connection to the AP Additional info: This problem did not occur on the previous kernel. The connection can be established when using the same encryption but no hidden bssid.
Created attachment 340251 [details] lspci -v
Do you happen to have access to any other hardware that uses mac80211-based drivers? If so, could you try using those to access the hidden SSID network? Could you try a wireless-testing kernel (with ath9k) as well? git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git Does that work any better than the rawhide kernel?
Currently I can not test it with a different hardware. I'll try to get the test with the different kernel done ...
I'm experiencing same kind of problem on Ubuntu 9.04 2.6.28-11-generic Network controller (lspci -v): Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Device 1a3b:1067, module = ath9k On Ubuntu 8.10 Intrepid (2.6.24-21-generic) it worked fine on same AP (with same settings)
I have similar issues with my laptop using the ath9k wireless card with Fedora 10. It would connect sporadically and fail to connect quite often after a cold boot. Restarting NetworkManager didn't help most of the time. In a RedHat class last week we removed the ath9k module with the modprobe -r ath9k command and reloaded it afterwards with modprobe ath9k and then it would connect just fine. Thought I would add to this report in case this info helps at all.
Please report back on how it went with wireless-testing or compat-wireless: http://wireless.kernel.org/en/users/Download
Hello again, My problem was resolved after moving to Fedora 11 pre-release.
Thanks, please close the bug report.