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 721193 - Manually set WiFi MAC address gets spontaneously replaced with the original one on AR2425
Manually set WiFi MAC address gets spontaneously replaced with the original o...
Status: RESOLVED DUPLICATE of bug 708820
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Reported: 2013-12-29 09:48 UTC by Yuri
Modified: 2014-01-02 11:23 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Yuri 2013-12-29 09:48:49 UTC
When I set the MAC address of the interface with the command 'ifconfig wlan0 hw ether NN:NN:NN:NN:NN:NN' and NetworkManager is running, NetworkManager resets the MAC to its original value when later this interface is brought down at some point.

This doesn't happen without the NetworkManager. So if the NetworkManager service is stopped before and restarted after the MAC change, this problem doesn't occur.

But the fact that NetworkManager would reset the MAC is bothersome, and is indicative of the wrong behavior. Once the user changes the MAC, NetworkManager should not be resetting it since there is no reason for it to assert the original MAC. The most NetworkManager can do is to memorize the new MAC and to use it for whatever it is using them.

I searched for SIOCSIFHWADDR in NetworkManager sources and didn't find it. So most likely this is done from some library called from the NetworkManager.

Mint distro.
Comment 1 Thomas Haller 2014-01-02 11:23:41 UTC
I am closing this bug as duplicate of bug 708820 and I'd suggest to follow up there.

If you disagree, feel free to reopen this one (explaining what's the difference).

Btw. the exact version of NetworkManager you are using on Mint is important to know too.

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