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 695038 - network: don't use nm-connection-editor for bridges
network: don't use nm-connection-editor for bridges
Status: RESOLVED DUPLICATE of bug 747443
Product: gnome-control-center
Classification: Core
Component: Network
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-03 00:42 UTC by Matthias Clasen
Modified: 2015-04-07 12:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Clasen 2013-03-03 00:42:10 UTC
need to add a bridge page to our connection editor.
Comment 1 Dan Winship 2013-03-04 13:30:25 UTC
This requires design, because the bridge connection has slave connections.

In nm-c-e, the bridge page of the editor has a list of the slave connections, with Add/Edit/Remove buttons next to it (basically just like the main connection-editor list, but as a flat list rather than a tree), and adding/editing a slave connection pops up a second editor window. Presumably the Add/Remove would turn into [+|-]... or I guess maybe [+|*|-] (where the "*" is a gear, for "Edit")?

We could also show the details of the slave connection inline rather than showing only a list and having the details in a separate window, but it seems like that would get very busy visually.

Also, when adding a slave, you have to ask what kind of slave to add... we can use the same type of dialog we use for the main [+] button, but we'd have to add Ethernet, Wi-Fi, etc to it as well, since you can bridge any of those types together.
Comment 2 Matthias Clasen 2013-04-24 00:48:21 UTC
Allan, an thoughts on this ?
Comment 3 Bastien Nocera 2015-04-07 12:28:06 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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