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 698112 - cli: bridge-slave and bond-slave interface types don't match real NM types
cli: bridge-slave and bond-slave interface types don't match real NM types
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: nmcli
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on: 682052
Blocks: tracker-nmcli
 
 
Reported: 2013-04-16 08:40 UTC by Pavel Simerda
Modified: 2020-11-12 14:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pavel Simerda 2013-04-16 08:40:29 UTC
With the 'cli-enhance' branch, 'nmcli connection add help' shows 'bond-slave' and 'bridge-slave' interface types seem to be made up as there are no such types in NetworkManager. The syntax is ambiguous as it doesn't indicate whether the real type will be ethernet, wifi or whatever else we support as a bridge/bond slave in the future.

My suggestion is to remove those two types and use 'master' as an option to any interface type (NM will determine whether that combination of master/slave types is valid).

I think this will require the 'slave-type' option to be optional, which is already reported.
Comment 1 Dan Winship 2013-05-02 15:59:47 UTC
NM bugzilla reorganization... sorry for the bug spam.
Comment 2 André Klapper 2020-11-12 14:31:42 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).