desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #132864
[Bug 1485558] Re: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10
Summary: more trouble, nm-applet menu starts to fill with irrelevant
vboxnet0 entries.
Details
Now nm-applet shows 5 "vboxnet0" ethernet connections, though I've not
created any of them. 4 of them show ipv4 parameters "disabled", ipv6
parameters "ignore". Only the currently auto-activated one shows ipv4
"manual" with correct IP address.
Suspending then resuming the Ubuntu machine still breaks the vboxnet0
connection to the VM.
Asking virtualbox to suspend the guest VM then resuming it still
reconfigures the connection which then works. And that causes *another
extra* "vboxnet0" entry in nm-applet list of connections. I can suppress
it manually but they should not be there in the first place.
Note: /etc/NetworkManager/system-connections/ now contains entries for
the real connections I've created, but none of these "vboxnet0"
connections.
Thank you for your attention.
** Summary changed:
- NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10
+ NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10, nm-applet fills with irrelevant entries.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1485558
Title:
NetworkManager breaks vboxnet* connections since 15.04, worked in
14.04 and 14.10, nm-applet fills with irrelevant entries.
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
On an Asus laptop running a freshly installed Ubuntu 15.04 64-bit, nm-
applet shows that NetworkManager wants to manage vboxnet0 and
vboxnet1. These are created by virtualbox which runs some guest OS
inside a VM. On previous Ubuntu releases, network-manager did not try
to manage them and there was no problem.
# Observed behavior
* nm-applet shows spinning animation for a long time, while it is not relevant. Clicking on "disconnect" in the menu unconfigures the interface which breaks it.
* after suspend-resume of the host, vboxnet* lose their correct configurations. vboxnet0 (a host-only interface where virtualbox runs a private dhcp server) gets a different IP address. Looks like https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1460750 but does not feel like a bug in virtualbox.
# Expected behavior
* Just like in 14.04 and 14.10, these interfaces are just ignored by
network-manager and they just work.
# Additional information
* After reading http://superuser.com/questions/9720/disabling-
networkmanager-for-a-specific-interface tried to add these lines to
/etc/network/interfaces. Even after restarting network-manager, it has
no effect.
iface vboxnet0 inet manual
iface vboxnet1 inet manual
So, reverted the change.
* Tried from https://blogs.gnome.org/dcbw/2015/02/16/networkmanager-
for-administrators-part-1/ to add in /etc/NetworkManager/conf.d/ a
file 50-virtualbox.conf containing the following lines. Even after
restarting network-manager, it is ignored.
[keyfile]
unmanaged-devices=vboxnet0,vboxnet1
* This is not eactly like https://www.virtualbox.org/ticket/13873, I'm not using Vagrant.
* Booting to 14.04 or 14.10 (that have been kept intact on the same machine) things just work as expected.
* /usr/share/doc/network-manager/NEWS.gz states that "'veth' interfaces are now unmanaged by default to cooperate better with external tools". Should vboxnet* be treated the same ?
* This seems on the topic but unclear to me: https://bugzilla.gnome.org/show_bug.cgi?id=731014
Thank you for your attention.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu15.1
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
Date: Mon Aug 17 13:13:04 2015
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2015-08-15 (1 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
IpRoute:
default via 192.168.47.1 dev wlan0 proto static metric 1024
169.254.0.0/16 dev vboxnet0 scope link metric 1000
192.168.47.0/24 dev wlan0 proto kernel scope link src 192.168.47.6
192.168.56.0/24 dev vboxnet0 proto kernel scope link src 192.168.56.102
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
LANGUAGE=fr_FR
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1485558/+subscriptions
References