GNOME Bugzilla – Bug 677150
network: make sure ipoib is handled
Last modified: 2012-12-17 13:13:56 UTC
NetworkManager supports bridging nowadays; the network menu should show something reasonable when it meets such a network configuration. 'Reasonable' might very well be 'just like wired' here. See http://fedoraproject.org/wiki/Features/NMEnterpriseNetworking (Note: this bug is part of a series of bugs I'm filing for handling 'exotic' network constellations)
s/bridging/IPoIB/
The only real question here is whether to mix ethernet and IPoIB devices together, or to have separate "Ethernet" and "IPoIB" sections (see also bug 677151). Assuming the machine has both ethernet and ipoib (which it probably does, since everything has onboard ethernet these days), then there isn't really even that much difference between the two approaches, since multiple ethernet devices already get split up into separate menu sections anyway. The only difference is that one way the sections would be labelled "Ethernet" and "InfiniBand", and the other way they'd be labelled "Intel 82579LM Gigabit" and "Mellanox Blah Blah Whatever".
Created attachment 230657 [details] [review] network: add minimal support for InfiniBand If present, InfiniBand devices show up with the ethernet devices (and the presence of an InfiniBand connection will cause "Wired" to be renamed to "Ethernet").
Review of attachment 230657 [details] [review]: ::: js/ui/status/network.js @@ +630,3 @@ +}); + +const NMDeviceWired = new Lang.Class({ Can't we have a NMDeviceInfiniband to implement the device specific auto-connection code? Or is it impossible to add-and-activate an infiniband connection?
In theory NM supports autoconnect of infiniband, but in reality, anyone with an infiniband connection will have configured it at install time.
(In reply to comment #5) > In theory NM supports autoconnect of infiniband, but in reality, anyone with an > infiniband connection will have configured it at install time. A similar theory holds for wired too, yet nm-applet has always included code to add a new connection if needed, and I dragged it into gnome-shell when I wrote the indicator originally. Should that be removed as well? Will NM ensure that something is always configured for each wired-like device in the system (maybe with autoconnect=false)?
(In reply to comment #6) > (In reply to comment #5) > > In theory NM supports autoconnect of infiniband, but in reality, anyone with an > > infiniband connection will have configured it at install time. > > A similar theory holds for wired too It's not ethernet vs infiniband, it's server use cases vs desktop use cases. Autoconnect was designed for desktop users, but infiniband only exists on server-class hardware. (And yes, there are enterprise users who run desktop environments on their servers, so putting minimal InfiniBand support into the shell isn't totally pointless.) At any rate, for an infiniband connection you need to configure whether to use datagram or connected mode anyway (and in the future possibly additional options), so if we wanted to do autoconnect, we'd have to add code to try one, and then if it doesn't work, try the other. (And then no one would ever use the feature because they already configured their infiniband connections at install time.)
Uhm, I see what you mean now, and it's a fine for me. Consider the patch accepted-commit_now.
Attachment 230657 [details] pushed as 8a1b834 - network: add minimal support for InfiniBand