Description of problem:
The RHEL documentation doesn't contain any piece about setting up wireless
connections. This is especially important for business users that install RHEL
on a laptop.
This piece of documentation should contain canonical ways to:
- quickly test hardware compatibility (how should I find out if this particular
laptop has a supported wireless card *before* buying the laptop ?)
- install and configure the wireless connection (via included graphical tools
*and* command line)
- test and troubleshoot the wireless connection
- measure and find out and configure wireless parameters, such as signal meter,
Version-Release number of selected component (if applicable):
Revision 5.1.0-1, Tue Jun 26 2007
Moving to 6.0.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
I will address your points in order.
The Deployment Guide now has a section on setting up wireless
There is a hardware compatibility list (https://hardware.redhat.com) but it does not include Wi-Fi. Besides searching on-line, you can ask your support representative to
help with this request. This is not easy to document as it is subject to rapid change.
3] The GUI method, i.e. using NetworkManager, is now covered in Chapter 7 of the Deployment Guide. As to documenting a CLI method, Chapter 8 now contains more information needed to do that: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Deployment_Guide/index.html#ch-Network_Interfaces
4 and 5] This is not something we feel the documentation team can deal with. Please ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
I propose to close this bug as "fixed, current release". Please let us know here if you would like to comment on the response above. Please raise new bugs if you find any errors or omissions.