Description of problem: In areas with many overlapping wifi networks, the performance of 2.4Ghz connections may be far worse than 5Ghz even though the signal level is stronger. For instance, ping times to the local router of 20000ms vs 100ms. Ideally the wifi drivers would be able to recognize the level of noise and/or congestion and switch over automatically, but failing that I would like to be able to explicitly request 5Ghz only. It seems that I can do this from the command line with nmcli con mod <SSID> 802-11-wireless.band a but it would be good to have this in the GUI as well. And to lean on driver writers to support this setting. I suppose I could select a particular BSSID, but that's more specific than I'm looking for. Version-Release number of selected component (if applicable): NetworkManager-1.8.2-1.fc26.x86_64 How reproducible: Always Steps to Reproduce: 1. Open wifi connection settings 2. Go to Identity tab 3. Actual results: No "Band" option Expected results: "Band" option Additional info:
"GUI" here means nm-connection-editor? From the description it sounds more like gnome-control-center. Gnome especially aims to omit advanced settings from the GUI. To me, this setting seems rather advanced even for nm-connection-editor.
I was looking at Gnome settings, but either GUI would be fine. This seems to me like a fairly common desire; often routers seem to deal with the absence of such a setting by defaulting 2.4Ghz and 5Ghz bands to different SSIDs, but usually I want to switch between them transparently, and often I don't control the router. FWIW, the Intel Windows wifi software has a Preferred Band advanced option.
Created attachment 1347016 [details] [PATCH] editor: allow setting band and channel also for client Wi-Fi I think there's no reason not to allow editing Band in GUI. It was implemented for Ad-Hoc networks. So, it is easy to show the pieces for infrastructure networks as well.
merged: https://git.gnome.org/browse/network-manager-applet/commit/?id=e552c19962e70c7133b16b2581516720dd7d43b5 Thanks!!
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.