Network manager shows and connects to virtual interfaces
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
High
|
Alexander Sack | ||
Jaunty |
Fix Released
|
High
|
Alexander Sack |
Bug Description
Binary package hint: network-manager
In the Hardy version of HAL currently it reports virtual network interfaces like the one created by libvirt. This interface shows up as a wired interface, with the name "Unknown computer." This make network manager choose it over better choices, though it never connects to the network properly.
There is some discussion about where these interfaces should go. If one is using crazy virtual networks NetworkManager should be able to connect to them, but it's unlikely most desktop users would use them. This is mostly likely a feature that would be used by advanced users in unusual setups. So the solution might be to just hide them.
The other question is in how virtual networks are shown in HAL. Since the patch has not been accepted upstream, this may change, and any detection code may become moot.
Workarround (by cjwatson):
|| libvirt will create a new vnet0 network interface. To stop this
|| confusing network-manager, add this stanza to the end of
|| /etc/network/
||
|| iface vnet0 inet manual
Related branches
Changed in network-manager: | |
milestone: | none → jaunty-alpha-6 |
I have a feeling this problem is what was causing my vmnet interfaces to not initialize correctly as well. I ended up having to add definitions in interfaces for my vmnet1 and vmnet8 or they came up w/o IP configured, as well in kdenetworkmanager they showed up in the list of configurable devices which they never did before.
Now that I have static assignments for them they don't show up in kdenetworkmanager any longer.