After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 790961 - Allow configuring wifi.scan-rand-mac-address from GUI
Allow configuring wifi.scan-rand-mac-address from GUI
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
git master
Other Linux
: Normal enhancement
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: 781295
 
 
Reported: 2017-11-28 22:00 UTC by Jeremy Bicha
Modified: 2020-11-12 14:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeremy Bicha 2017-11-28 22:00:41 UTC 
Ubuntu 17.10 has set wifi.scan-rand-mac-address=no because of issues with the feature on some hardware, especially with older versions of NetworkManager like the 1.4.4 version shipped in 17.04.

I'm hesitant to re-enable this feature in Ubuntu as long as
A) we don't know for sure which drivers are affected,
B) and more importantly, there is no GUI way to turn the feature on or off. Asking users to edit config files isn't very nice.

Therefore, I'm requesting that at least gnome-control-center have an on/off switch for this feature.

See also bug 785117 for how the Connectivity Check feature was exposed in a way that gnome-control-center could have an on/off switch.
Comment 1 André Klapper 2020-11-12 14:32:00 UTC 
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).