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.

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

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 ***