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 736909 - Ethernet: please add ability to specify capabilities to advertise.
Ethernet: please add ability to specify capabilities to advertise.
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: API
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-09-18 14:08 UTC by jmranger
Modified: 2020-11-12 14:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jmranger 2014-09-18 14:08:16 UTC
(initially reported at https://bugs.kde.org/show_bug.cgi?id=338881)

When configuring a wired ethernet connection, networkmanagemer already offers to specify whether autonegotiation should be performed, and if not, the specific configuration (speed, duplex) to use.

It is currently possible (at least with ethtool [0] - see "advertise") to keep autonegotiation on, but to limit to specific speed. This capability isn't available in networkmanager.

Use-case: in a home setup with a single computer and a single handheld device that never talk to each other, gigabit ethernet doesn't provide any performance gain, but has a real (even if marginal) energy cost.

My ideal scenario (that I currently achieve through modifications to the ifup script) is to have autonegotiation ON and advertise capability 0x00F (i.e. all variants of 10 and 100 mbps).

Thanks!

[0] http://manpages.ubuntu.com/manpages/saucy/en/man8/ethtool.8.html
Comment 1 André Klapper 2020-11-12 14:27:38 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).