Bug 906133
| Summary: | Test case failure: nm-connection-editor - wireless - set BSSID | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Mark Gordon <mgordon> | ||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.4 | CC: | jklimes, kdube, pvine, rkhan, tpelka | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | NetworkManager-0.8.1-47.el6 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-11-21 21:48:49 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Mark Gordon
2013-01-30 23:24:15 UTC
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. It is a misunderstanding. BSSID field in the connection editor is for restricting ("locking") the connection to only the AP with specified BSSID (as indicated in the tooltip). It is not meant to create BSSID for Ad-hoc networks (I admit it could be a bit misleading).
Nonetheless, BSSID is random for ad-hoc networks. In fact, it is not created by NetworkManager, but in kernel mac80211 subsystem or driver (when Ad-hoc network is created). So, there's no need to specify the BSSID at all.
The code for generating BSSID for IBSS (Ad-hoc) is here:
http://lxr.linux.no/linux+v3.7.6/net/mac80211/ibss.c#L685
Yeah, we should probably just hide the BSSID field for AdHoc connections as we cannot guarantee that it will be honored. Created attachment 707201 [details]
[PATCH NM master] editor: hiding BSSID for Ad-Hoc connections
Patch for hiding BSSID for Ad-Hoc connections.
This is for NM upstream master branch.
Created attachment 707202 [details]
[PATCH RHEL 6] editor: hiding BSSID for Ad-Hoc connections
Backport of the previous patch to RHEL 6.x NM.
(In reply to comment #5) > Created attachment 707201 [details] > [PATCH NM master] editor: hiding BSSID for Ad-Hoc connections > > Patch for hiding BSSID for Ad-Hoc connections. > This is for NM upstream master branch. Looks good, please push to git master and nm-0-9-8. (In reply to comment #6) > Created attachment 707202 [details] > [PATCH RHEL 6] editor: hiding BSSID for Ad-Hoc connections > > Backport of the previous patch to RHEL 6.x NM. Looks good. (In reply to comment #7) > (In reply to comment #5) > > Created attachment 707201 [details] > > [PATCH NM master] editor: hiding BSSID for Ad-Hoc connections > > > > Patch for hiding BSSID for Ad-Hoc connections. > > This is for NM upstream master branch. > > Looks good, please push to git master and nm-0-9-8. fa3a6b876b095d087d7eb179246d78c3d3e58534 (master) 0b93ea3f6139dd46a418a108ee9e01c9098691d9 (nma-0-9-8) 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. http://rhn.redhat.com/errata/RHBA-2013-1670.html |