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 702702 - nm-applet fails to alert the user when the Cloned MAC address cannot be set
nm-applet fails to alert the user when the Cloned MAC address cannot be set
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: nm-applet
0.9.8
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-06-19 23:07 UTC by Forest
Modified: 2020-11-12 14:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Forest 2013-06-19 23:07:45 UTC 
I have a netbook whose wifi driver seems to be refusing to allow a custom MAC address to be set.  The Network Manager applet allows me to enter a value in the "Cloned MAC address" field, but when it comes time to actually set the MAC address and the driver doesn't accept it, the applet fails to notify me of the problem and exposes my hardware MAC address to the wireless network anyway.

NetworkManager does log the problem to syslog, but relatively few users will notice this because the UI makes it look like everything worked just fine, and it doesn't solve the problem of quietly exposing the hardware MAC address without the user's permission.
Comment 1 André Klapper 2020-11-12 14:27:07 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).