desktop-packages team mailing list archive

[Franck <alci@xxxxxxxxxx>]

Here is the feedback I got from the network-manager mailing list:

On Thu, 2015-03-19 at 09:18 +0100, Franck Routier (perso) wrote:
> Hi list,
>
> I'm using Ubuntu and just upgraded to (still in development) Vivid.
> Now I see that network-manager handles my virbr0 bridge (libvirt), which 
> it didn't before.

NM will recognize and "manage" all network interfaces, but that does not
mean that NM actually touches the interfaces.  If the interface already
has a configuration, NM simply assumes the existing configuration and
waits for you to tell it to do something.  That's a difference from
older versions of NM (0.9.8 and earlier) where NM was mostly ignorant of
existing configuration.

We know that NM 0.9.10 still has a few edge cases where it touches
interfaces and shouldn't, but almost all of those have already been
fixed in NM 1.0 and later.

Dan

-- 
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/1432599

Title:
  Network-manager tries to manage virbr0, which it should not

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Fedora:
  Unknown

Bug description:
  Since a recent upgrade in vivid, nm is trying to manage virbr0. This
  results in my main machine not getting a real IP address on eth0, and
  virtual machines not being able to use the network.

  This is probably related to
  https://bugzilla.redhat.com/show_bug.cgi?id=1166199

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 16 12:36:07 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-13 (92 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 10.0.0.1 dev eth0  proto static  metric 1024
   10.0.0.0/24 dev eth0  proto kernel  scope link  src 10.0.0.75
   192.168.111.0/24 dev wlan0  proto kernel  scope link  src 192.168.111.8
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  http_proxy: http://localhost:8118/
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
  no_proxy: localhost,127.0.0.0/8,::1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions