Bug 999997

Summary: NM ignores the profile's channel setting and connects to wifi network
Product: Red Hat Enterprise Linux 7 Reporter: Vitezslav Humpa <vhumpa>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: dcbw
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-31 14:06:56 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:

Description Vitezslav Humpa 2013-08-22 13:50:39 UTC 
Description of problem:
In nmcli, setting the 802-11-wireless.channel property to a specific channel should result for the profile to only connect to networks on the channel specified. However, currently this setting is ignored and profile is used to successfully connect to a same SSID wifi network on different channel as well.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.0-9.git20130807.el7.x86_64

Steps to Reproduce:
1. nmcli connection add type wifi ifname yyy con-name xxx autoconnect off ssid xxx
2. nmcli connection edit xxx
3. nmcli> set 802-11-wireless.band bg
4. nmcli> set 802-11-wireless.channel 11 #(any other than the network is on)
5. Save and quit, nmcli connection up xxx

Actual results:
Profile connects normally

Expected results:
It does not, as the network does not fit the profile
Comment 1 Dan Williams 2013-08-31 14:06:56 UTC 
At the moment, NM doesn't allow locking the channel or band of an access point due to kernel/driver and supplicant restrictions, except for AdHoc and Hotspot connections where the channel is determined by the local machine.  These parameters should be hidden from nmcli when the wifi mode is "infrastructure".  I'm going to dupe this bug to 1000096 since the problem is actually the same.

*** This bug has been marked as a duplicate of bug 1000096 ***