Red Hat Bugzilla – Bug 812259
add option to disable 5GHz band to iwlwifi
Last modified: 2012-06-20 04:46:48 EDT
Description of problem:
Wireless roaming between 2.4GHz AP and 5Ghz AP cause mac80211 and iwlwifi (driver and firmware) malfunction, there are various subtle and hard to fix bugs (bug ). Until those will be fixed, allow to disable 5Ghz band, hence prevent to associate to 5Ghz AP. This can workaround problems with wireless roaming, when APs are dual-band and roaming will be done within 2.4 GHz band.
modprobe iwlwifi 5ghz_disable=1
After that, 5Ghz operation will be disabled, wireless network scan will not show any 5GHz APs, so we will not able to associate to that APs.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
Created attachment 577961 [details]
Proposed patch (for RHEL6.2)
To be clear so we can implement this correctly, the actual kernel module is named iwlagn.
Can you confirm that the /etc/modprobe.d/wireless.conf setting should be
options iwlagn 5ghz_disable=1
Yes, correct RHEL6 driver name is iwlagn (on upstream driver was renamed to iwlwifi).
Patch(es) available on kernel-2.6.32-266.el6
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Various problems were discovered in the iwlwifi driver happening in the 5 GHz band. Consequently, roaming between access points (AP) on 2.4 GHz and 5 GHz did not work properly. This update adds a new option to the driver that disables the 5 GHz band support.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.