GNOME Bugzilla – Bug 706868
Multiple "unknown" interfaces in Network screen
Last modified: 2013-09-10 19:55:11 UTC
Hi, I've just upgraded to Fedora-20, and I noticed there are 2 unknown interfaces in the Network screen. All 3 of these are quite common, so it would be nice if they would be handled better. The 3 I have are: Unknown (virbr0-nic) - this is a part of the standard networking setup libvirt does Unknown (tun0) - this is caused by the NetworkManager managed vpnc vpn connection I'm using Unknown (lo) - the venerable loopback interface Regards, Hans
I'm also seeing Unknown (sit0) in my vm.
(In reply to comment #0) > Unknown (virbr0-nic) - this is a part of the standard networking setup libvirt Hi Hans, I think this is ok to be 'unknown' or 'foreign', do you suggest to hide it or to display it with more specific information? > does > Unknown (tun0) - this is caused by the NetworkManager managed vpnc vpn > connection I'm using I guess you would suggest to hide it as it's part of an active connection, right? > Unknown (lo) - the venerable loopback interface This is a special one. I think we should start managing the loopback device and allow configuration of *additional* addresses on top of the kernel-generated ones. It's often useful to attach additional addresses to loopback as opposed to special dummy interfaces. I'd like to here more UI-centric views on that, though. (In reply to comment #1) > I'm also seeing Unknown (sit0) in my vm. My opinion is that we should do our best to prevent kernel modules from auto-creating devices in modern distributions. They usually serve no purpose except in absence of [knowledge of] tools to create them.
Hi Pavel, (In reply to comment #2) > (In reply to comment #0) > > Unknown (virbr0-nic) - this is a part of the standard networking setup libvirt > > Hi Hans, > > I think this is ok to be 'unknown' or 'foreign', do you suggest to hide it or > to display it with more specific information? Either one will work, either show it with some more information and otherwise immutable, or just hide it, I just think showing an interface which will be present on many many systems as unknown is counter productive. > > does > > Unknown (tun0) - this is caused by the NetworkManager managed vpnc vpn > > connection I'm using > > I guess you would suggest to hide it as it's part of an active connection, > right? Right. > > > Unknown (lo) - the venerable loopback interface > > This is a special one. I think we should start managing the loopback device and > allow configuration of *additional* addresses on top of the kernel-generated > ones. It's often useful to attach additional addresses to loopback as opposed > to special dummy interfaces. That sounds very advanced user to me, I would expect an advanced user to use some advanced tool for this, like calling nm-connection-editor directly. I would just hide it, but that is just my 2 $-cents. Regards, Hans
the control center should ignore all devices of type NM_DEVICE_TYPE_GENERIC
Will you come up with a patch for this, Dan ?
Created attachment 254593 [details] [review] network: don't show unmanaged devices And in particular, in NM 0.9.10, don't show NM_DEVICE_TYPE_GENERIC devices. ====== (not tested because I don't have a new-enough jhbuild environment to be able to build current gnome-control-center.)
(In reply to comment #6) > Created an attachment (id=254593) [details] [review] > network: don't show unmanaged devices > > And in particular, in NM 0.9.10, don't show NM_DEVICE_TYPE_GENERIC > devices. > > ====== > > (not tested because I don't have a new-enough jhbuild environment to > be able to build current gnome-control-center.) Bummer, I don't have a new-enough NM in my system to test this against. But the patch looks obvious enough to me.
Review of attachment 254593 [details] [review]: Looks good to me.
Attachment 254593 [details] pushed as fea9da1 - network: don't show unmanaged devices