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 731057 - Bridges can't be forced to have fixed MAC addresses
Bridges can't be forced to have fixed MAC addresses
Status: RESOLVED DUPLICATE of bug 729844
Product: NetworkManager
Classification: Platform
Component: general
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-05-31 21:50 UTC by Philip Prindeville
Modified: 2014-06-01 19:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Philip Prindeville 2014-05-31 21:50:17 UTC 
Looking at the bridges configuration state, a MAC address doesn't seem to be one of the attributes.

This is unfortunate, since if you're using virtualization (KVM+virt-manager, for instance) for network testing with bridges between VM instances, you'd want to have your bridges always come up with the same MAC addresses for reproducibility in automated testing.

I've also tried to create a slave Ethernet device called "vnet0" and bind it to the bridge, but every time I do:

nmcli connection edit "Virtual Ethernet 0"
set connection.master 66ce6658-36f7-8b22-55c4-48c55a074e14
save
quit
nmcli connection edit "Virtual Ethernet 0"
print connection

the "master" attribute has gone away.
Comment 1 Dan Winship 2014-06-01 19:04:45 UTC 
In one of those crazy timing coincidences that occasionally happens, this was fixed in git master on Friday. :)

(There will be a 0.9.10 release some time this month, which will include this functionality.)

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