Red Hat Bugzilla – Bug 503823
Joining hidden SSID network using wpa_supplicant/NetworkManager requires module load options for iwlagn adapter
Last modified: 2010-06-28 08:47:39 EDT
Description of problem:
Could not join hidden SSID networks with the intel wireless 4965agn adapter.
Version-Release number of selected component (if applicable):
Using kernel-22.214.171.124-167 with latest updates on Fedora 11 RC as of 2 June 2009.
Installed on Dell Vostro 1510 laptop with IWL4965AGN wireless adapter.
Steps to Reproduce:
1. Configure wpa_supplicant.conf to use a hidden SSID network
2. restart wpa_supplicant
4. give up
Unable to join hidden SSID networks.
Should be able to join hidden SSID networks.
I was able to get wpa_supplicant to work correctly using a work-around.
1. add install iwlagn /sbin/modprobe --ignore-install iwlagn amsdu_size_8K=1 to
2. stop NetworkManager or (network and wpa_supplicant services)
3. rmmod iwlagn
4. modprobe -a iwlagn
5. start NetworkManager or (network and wpa_supplicant services)
6. search for and join hidden SSID networks
I can confirm this on a different notebook (HP 8710p) with the same wireless card.
It only fails to connect to hidden networks - you use the gnome applets to start connecting and it stays in "connecting mode" forever.
If I make the network broadcast itself to the world, it connects successfully and runs great.
I can also Confirm, after today updates, lenovo thinkpad R61, intel 4965, iwlagn.
It only fails to connect to hidden networks, now it does nothing, doesn't even search when i connect to hidden network.
If I make the network broadcast itself to the world, it connects successfully
and runs great.
In home i can fix it, but in work i cant connect, and have to use cable.
Note i Have Fedora x86_64 = 126.96.36.199-213.fc11.x86_64
I managed to grab the hidden wireless by BSSID, the mac address of the wireless device.
i hope it holds, NetworkManager should have a scan button...even for hidden networks like iwlist.
Is this still an issue with latest 188.8.131.52 kernels that are available as Fedora 11 updates? This issue is more a driver problem than a supplicant problem. If it's still present with 184.108.40.206 and later, please make sure you check the "I'm providing the requested information button" so that the bug is no longer in NEEDINFO state.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
I can confirm that it has been fixed during the Fedora 12 cycle. I cannot pinpoint exactly when the situation changed, but it is fixed for me.
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.