#756161 network-manager: incorrectly thinks I'm connected just because libvirt bridge is up

Package:
network-manager
Source:
network-manager
Description:
network management framework (daemon and userspace tools)
Submitter:
"brian m. carlson"
Date:
2014-08-01 01:39:05 UTC
Severity:
normal
#756161#5
Date:
2014-07-26 22:50:14 UTC
From:
To:
I have libvirt installed on my laptop so that I can easily manage my KVM
virtual machines.  This results in a virbr0 device that is up all the
time.  It's assigned a static RFC 1918 IP address that fits in with the
rest of my network.

Most of the rest of the time, I use wlan0 to connect to a wi-fi network,
whether I'm at home or not.  If the wi-fi is not working (say, I'm on an
airplane), network-manager still thinks I'm connected just because
virbr0 is up.

This isn't very useful, and it wasn't until a recent network-manager
version that it even considered virbr0 at all.  (I presume libvirt took
care of everything before.)  network-manager should just ignore this
device and not falsely claim that the network is up.
#756161#10
Date:
2014-08-01 01:30:53 UTC
From:
To:
I'm also seeing this on Debian jessie as of a recent update. A
workaround for me was to ignore the virbr0 interface in
/etc/NetworkManager/NetworkManager.conf:

  [main]
  plugins=ifupdown,keyfile

  [ifupdown]
  managed=false

  [keyfile]
  unmanaged-devices=interface-name:virbr0

Hopefully we can find a way to revert to the previous behavior, which
did not require a workaround.