When an interface is configured outside of NetworkManager's knowledge
(like libvirt's or docker's bridge), then NetworkManager generates an
in-memory connection profile and pretends(!) that this is active. This
is to show that something is going on with the device, and
NetworkManager is supposed to
In previous versions of GNOME (such as the version in RHEL 7.6), an
active NetworkManager connection profile for virbr0 caused a wired
Ethernet connection to appear in the top bar in GNOME Shell. It seems
this is actually now suppressed, and GNOME Control Center does not
expose the virbr0 device on
This has remained reproducible in every release from Fedora 23 through
Fedora 30 -- the problem never went away (and the underlying
reason/behavior never changed). Please re-open against Fedora 30.
This occurs in Fedora Workstation when it is installed to disk. The
behavior can be very easily seen
(NB: I'm a libvirt developer, so I'm writing this comment from that POV)
1) You should never need to create (actually *shouldn't* create) an
ifcfg-* file for a libvirt-created bridge. If proper operation requires
this, then there is definitely a bug.
2) NetworkManager should never mess around wit
Launchpad has imported 26 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1166199.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
This affected me when I went from Xubuntu 15.10 to 16.04; the wired
network icon would be shown whenever I wasn't connected to any actual
networks, and adding the config tweak in #4 triages the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
For me this happened after upgrade from 15.04 to 15.10.
Adding suggested fix to NetworkManager.conf solved the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1
The "
/etc/NetworkManager/NetworkManager.conf
[keyfile]
unmanaged-devices=interface-name:virbr0
"
indeed does the trick.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net
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 did
Taking a cue from https://bugzilla.redhat.com/show_bug.cgi?id=1166199 I
worked around the issue by adding the following to my
/etc/NetworkManager/NetworkManager.conf
[keyfile]
unmanaged-devices=interface-name:virbr0
Yet I imagine that the real solution is something more general.
** Changed i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://
** Bug watch added: Red Hat Bugzilla #1166199
https://bugzilla.redhat.com/show_bug.cgi?id=1166199
** Also affects: network-manager (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1166199
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
Here is a bug report, related to the subject:
https://bugzilla.gnome.org/show_bug.cgi?id=731014
Notice vboxnet0 also appears in nm-applet, but is shown as Unmanaged,
unlike virbr0.
** Bug watch added: GNOME Bug Tracker #731014
https://bugzilla.gnome.org/show_bug.cgi?id=731014
--
You received
** Description changed:
- Since a recent upgrade in vivid, nm is tryoing to manage virbr0. This
+ 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.
Public bug reported:
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
Prob
15 matches
Mail list logo
