Hide Forgot
Description of problem: Adding a new bridge connection via Network Manager GUI under Gnome adds a bridge but it is never started. This is exactly the same of Bug 1036961 which was closed due to Fedora 21 EOL but it's still around on F24. Plus, the suggestion to bring the bridge slave up via nmcli does not work anymore. Version-Release number of selected component (if applicable): 1.2.4-3.fc24 How reproducible: Always Steps to Reproduce: Click Network in Gnome Settings Click the Plus button in the lower left Click Bridge I see a dialog called "Editing Bridge connection 1". Next to the "Bridged Connections" panel, click the "Add" button. I expect this to add an existing interface to the bridge. A dialog appears that says "Select the type of connection you wish to create" - I want to add an ethernet connection to the bridge, so I select "Ethernet" in the dropdown. The options are "Create..." and "Cancel". I click "Create..." This opens a dialog titled "Editing bridge0 slave 1". The options are "Device MAC address", "Cloned MAC address", and "MTU". Now, as an average user, I'm pretty lost but let's try to take a guess... In the "Device MAC address" I click the dropdown arrow. I see the MAC address of my ethernet device with "(enp0s31f6)" next to it. I select it. I click "Save..." I am back in the "Editing Bridge connection 1" dialog. I click "Save..." (I'm aware I have added only one interface, but lets see if that works). I click "Save..." in the bridge dialog. Actual results: I have a bridge. It can never establish a connection. It seems to have no interfaces connected. $ brctl show bridge name bridge id STP enabled interfaces bridge0 0080.000000000000 yes Expected results: A bridge is created and associated with the ethernet device indicated in the set up dialog. Additional info: The bridge can be set up by forcing its state up with nmcli: $ nmcli con show NAME UUID TYPE DEVICE Bridge connection 1 39b61f8f-d5c4-4d90-88e2-bb497cfd4744 bridge bridge0 enp0s31f6 4a104510-8889-4db2-bc97-fe523a18ae99 802-3-ethernet enp0s31f6 bridge0 slave 1 825fd23b-5ca0-4978-b35c-4313128f5e3a 802-3-ethernet -- Then, I try to set the slave up but there's no way to do it: $ nmcli con up 825fd23b-5ca0-4978-b35c-4313128f5e3a Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5) But why should a user use the GUI and then CLI?
Sorry there are a couple of typos. Using nmcli to bring the bridge slave up works.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.