RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 613491 - NetworkManager does not connect to wireless connection automatically
Summary: NetworkManager does not connect to wireless connection automatically
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Dan Williams
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-12 01:52 UTC by James G. Brown III
Modified: 2014-12-01 23:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-19 17:59:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description James G. Brown III 2010-07-12 01:52:00 UTC 
Description of problem:

NetworkManager does not connect to wireless connection automatically


Version-Release number of selected component (if applicable):

NetworkManager-0.8.1-2.el6.i686

How reproducible:

100%

Steps to Reproduce:
1. Start up Lenovo X60 it does not connect
2. or put to sleep and upon wake up it does not connect
3.
  
Actual results:

Connection needs to be manually started, although the connect automatically for the wireless network is selected. 

Expected results:

Wireless connection automatically connects when in range. 

Additional info:
Comment 2 Dan Williams 2010-07-12 22:13:34 UTC 
Is the wifi network you'd like to connect to a "hidden" or "non-broadcasting" network?

When this happens, can you run 'nm-tool' for me and paste/attach the output and indicate which AP you'd like to connect to?

Can you also include the last 20 lines or so of 'dmesg' when this occurs?
Comment 6 James G. Brown III 2010-07-12 23:17:16 UTC 
Dan, To further clarify the network is saved and available to manually connect. In order to manually connect I go to Edit Connections... Select the wireless tab and the network. Finally, I am prompted for root's password and then am able to hit connect. 

- James
Comment 7 Dan Williams 2010-07-12 23:44:30 UTC 
Can you grab the output of 'sudo iwlist wlan0 scan' from a terminal when NM does not automatically connect?  We need to see if the card is finding the AP at all; even if the AP doesn't broadcast it's name.

If you've connected to the AP at least once before, we should be caching it's BSSID and thus we can match up the scan result with the connection and connect automatically.  Apparently that's not happening.
Comment 10 Dan Williams 2010-07-14 14:44:49 UTC 
Do you know which AP is the hidden one you want to connect to?
Comment 11 James G. Brown III 2010-07-15 01:25:02 UTC 
Dan, It should be Cell 03 - Address: 00:13:10:8D:AD:B3 in the iwlist attachment. 

- James
Comment 13 Dan Williams 2010-07-21 21:42:38 UTC 
Could you attach:

gconftool-2 --dump /system/networking/connections

for me so I can verify that the AP's BSSID is stored in the previously-used-BSSIDs section of the config?
Comment 15 Dan Williams 2010-07-27 19:11:37 UTC 
Is the hidden SSID 'rh-wireless' or RH-WLAN-TRUST?

It looks like the hidden AP you want to connect to is not listed in the GConf configuration for any network, which means NM won't match it up with a scan result.  If you've connected to the AP at least once (or the card has automatically roamed to it) then the applet should scrape that BSSID and save it.  Have you used the "connect to hidden wireless network" item in the vicinity of this AP before?
Comment 19 Dan Williams 2011-02-03 22:00:11 UTC 
We need a bit more info here, if you wouldn't mind reproducing this when running NM manually if you can, then you can:

service NetworkManager stop
/usr/sbin/NetworkManager --no-daemon --log-level=debug

and we'll get a bunch of spew about what NM's doing for the WIFI.
Comment 21 RHEL Program Management 2011-10-07 15:57:25 UTC 
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 22 Dan Williams 2013-02-19 17:59:26 UTC 
Please reopen if you're able to get the requested information.  Thanks!
Note You need to log in before you can comment on or make changes to this bug.