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 678360 - Show interface names in the details page
Show interface names in the details page
Status: RESOLVED DUPLICATE of bug 677143
Product: gnome-control-center
Classification: Core
Component: Network
unspecified
Other Linux
: Normal trivial
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-06-18 23:09 UTC by dave_roberts20
Modified: 2012-09-27 20:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
For multiple devices, differentiate them with interface name (5.16 KB, patch)
2012-09-20 14:54 UTC, Jiri Klimes
needs-work Details | Review
[PATCH] display "Interface Name" for Ethernet and Wi-Fi devices (17.00 KB, patch)
2012-09-20 14:56 UTC, Jiri Klimes
accepted-commit_after_freeze Details | Review
[PATCH] use more specific names for device types (1.61 KB, patch)
2012-09-20 15:02 UTC, Jiri Klimes
needs-work Details | Review

Description dave_roberts20 2012-06-18 23:09:22 UTC
I'm running Gnome3 as a VirtualBox client with multiple wired network cards specified.  All the wired network cards are of the same brand/name.  

I've setup a description of the network card in the network settings manager(network-settings-manager->network settings->wired->connection name).

It would be great if it listed my name for the network connection in the network settings main dialog and also in the drop down list when pressing the icon on the toolbar.  At the moment it just shows the device name and if they're all the same name I have to dig around in the settings to see what network I'm actually connecting to.

Note that when creating a VPN it uses the description specified by the user correctly.
Comment 1 André Klapper 2012-06-19 07:42:14 UTC
Which exact version of NetworkManager is this about?
Comment 2 dave_roberts20 2012-06-19 23:12:06 UTC
Version: 0.9.4.1-0ubuntu2  (obtained from the package information)

Is there a way to determine the applet version from the command line?
"--version" doesn't seem to work and there's no about box.

This is the latest version from the Ubuntu 12.04 repos.
Comment 3 Jiri Klimes 2012-07-26 10:49:42 UTC
Yeah, the wired (and wifi too) devices should be differentiated with interface name and if connected with the connection name too.

The thing dwells in gnome-control-center.
Comment 4 Jiri Klimes 2012-09-20 14:54:34 UTC
Created attachment 224838 [details] [review]
For multiple devices, differentiate them with interface name

Show "Wired (eth0)", "Wired (eth1)" in list if there are more devices of the same type.
Comment 5 Jiri Klimes 2012-09-20 14:56:51 UTC
Created attachment 224839 [details] [review]
[PATCH] display "Interface Name" for Ethernet and Wi-Fi devices

It should probably be done for Mobile broadband as well (not done in this patch).
Comment 6 Jiri Klimes 2012-09-20 15:02:38 UTC
Created attachment 224842 [details] [review]
[PATCH] use more specific names for device types

Ethernet and Wi-Fi are wide spreadterms and are more specific than generic "Wireless" and "Wired".
Moreover, when devices such as InfiniBand or WiMax are added, the "Wireless" and "Wired" would become ambiguous.
The names should be changed on some more places as well. (And probably also in code not visible to users).
Comment 7 Matthias Clasen 2012-09-20 17:48:06 UTC
See bug 677143
Comment 8 Bastien Nocera 2012-09-20 21:06:12 UTC
Review of attachment 224838 [details] [review]:

I would rather that the differentiation was:
- first through type:
Wired
Wired
becomes:
Ethernet
Infiniband

- secondly through connection type:
Ethernet
Ethernet
becomes:
USB Ethernet
PCI Ethernet

- thirdly through vendor/product:
PCI Ethernet
PCI Ethernet
becomes:
Intel Ethernet
Realtek Ethernet

Finally through using interface names:
Intel Ethernet
Intel Ethernet
becomes:
Intel Ethernet (eth0)
Intel Ethernet (eth1)
Comment 9 Bastien Nocera 2012-09-20 21:06:58 UTC
Review of attachment 224839 [details] [review]:

Looks fine to commit after 3.6 has branched.
Comment 10 Bastien Nocera 2012-09-20 21:09:44 UTC
Review of attachment 224842 [details] [review]:

Ditto the other patch.
Comment 11 Bastien Nocera 2012-09-20 21:17:37 UTC
Renamed the bug, with the patch we want to keep, and I'll add comment 8 to bug with Dan's patches. Jiri, can you check with Dan about this?
Comment 12 Dan Winship 2012-09-27 20:48:23 UTC

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