FS#41397 - [networkmanager] tries to manage vboxnet0

Attached to Project: Arch Linux
Opened by acidicX (acidicX) - Wednesday, 30 July 2014, 12:38 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 10 June 2016, 23:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No

Details

Since yesterday's update to 0.9.10.0-2 NM tries to manage the vboxnet0 interface. This makes no sense and wasn't the case before. I guess it was blacklisted somehow and now it isn't anymore.

To solve this temporarily, I've added it to unmanaged-devices, but it still shows up in the NM list (but now as unmanaged). Before the update, it wasn't in the NM interface list at all.

I don't know if the problem comes from upstream, I've found no bug report there yet.

Steps to reproduce:
Start NM with VirtualBox installed

See also:
https://bbs.archlinux.org/viewtopic.php?id=184999
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 10 June 2016, 23:22 GMT
Reason for closing:  Fixed
Comment by kballou (l0x3py) - Friday, 01 August 2014, 21:46 GMT
I've noticed virtualbox as well as now docker. `nm-applet` will show `docker0` after starting the docker service, i.e., `#systemctl start docker`.
Comment by Dave Hardy (davehardy20) - Tuesday, 05 August 2014, 09:54 GMT
Also to add to this issue I have VMware Workstation 10.0.3 build-1895310 installed and after the update to Network Manager 0.9.10.0-2, Network Manger now manages the 2 virtual network adaptoprs vmnet1 and vmnet8.
As stated in the initial details this was not the case before the upgrade.
Comment by Daniel Graña (dangra) - Tuesday, 05 August 2014, 18:10 GMT
There is a bug report in NetworkManager tracker for this issue: https://bugzilla.gnome.org/show_bug.cgi?id=731014
Comment by Samantha McVey (samcv) - Friday, 10 June 2016, 22:37 GMT
This bug was fixed in 2015 in networkmanager as can be seen in the gnome bug report the previous poster linked to. Recommending this be closed.

Loading...