cryptic interface names in network-manager-applet

[Samium Gromoff]

Binary package hint: network-manager-gnome

"eth0", "eth1" etc. are not optimally descriptive names in the presence of multiple different NICs.

One would expect the NIC mfgr/model names provided along with the usual interface notation,
like: "eth0 (VIA Rhine)\neth1 (Intel EtherExpress 100)".

Applies to all releases, up to Jaunty alpha 3, all network-manager-applet versions, up to
0.7-0ubuntu1.

[Chris Coulson (chrisccoulson)]

"Auto eth0" is just the name of the default profile. You can add profiles and change the name to whatever you want. The applet already displays interface names when more than one interface is detected. It doesn't display interface names if only one interface is detected, as that doesn't make sense.

If you have more than one interface but the applet doesn't show interface names, then that is a bug. Is that the case?

I've attached a screenshot of my applet, to show you what it looks like when 3 interfaces are present. Notice that there is a name for each interface, and a profile associated with each.

[Samium Gromoff (deepfire)]

В Пнд, 19/01/2009 в 18:53 +0000, Chris Coulson пишет:
> "Auto eth0" is just the name of the default profile. You can add
> profiles and change the name to whatever you want. The applet already
> displays interface names when more than one interface is detected. It
> doesn't display interface names if only one interface is detected, as
> that doesn't make sense.

My bad, I confused nm-connection-editor with n-m-a.

I don't currrently have a box with >1 interfaces to check whether
n-c-e shows the interface names, but that wasn't the case in 8.10.

I'm sorry if this bug report sounds lousy.

> If you have more than one interface but the applet doesn't show
> interface names, then that is a bug. Is that the case?

No, I don't have anything to say about n-m-a, sorry.

regards, Samium Gromoff

[Michele Mangili (mangilimic)]

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it.