Description of problem: I have host system (hostname mother.pipebreaker.pl) with couple of libvirt-lxc containers. Every time I start a container, NM running on host runs dhclient on "veth*" interface associated with this container. Please note: this is NOT about dhclient started *inside* libvirt-lxc container. This is about dhclient being start on the host system. It looks like that: 2013-12-30T10:54:39+0100 mother.pipebreaker.pl NetworkManager[897] <info> (veth0): DHCPv4 state changed nbi -> preinit 2013-12-30T10:54:39+0100 mother.pipebreaker.pl dhclient[8627] Listening on LPF/veth0/e2:ac:7d:63:8d:2f 2013-12-30T10:54:39+0100 mother.pipebreaker.pl dhclient[8627] Sending on LPF/veth0/e2:ac:7d:63:8d:2f 2013-12-30T10:54:39+0100 mother.pipebreaker.pl dhclient[8627] Sending on Socket/fallback 2013-12-30T10:54:39+0100 mother.pipebreaker.pl dhclient[8627] DHCPDISCOVER on veth0 to 255.255.255.255 port 67 interval 3 (xid=0x7e26fb77 Version-Release number of selected component (if applicable): NetworkManager-0.9.9.0-22.git20131003.fc20.x86_64 libvirt-daemon-lxc-1.1.3.1-2.fc20.x86_64 How reproducible: Always. Steps to Reproduce: 1. Use virt-manager to create libvirt-lxc container 2. Start the container 3. Actual results: dhclient is started on "veth0" interface on host. Expected results: dhclient should no be started on host. Additional info: "veth*" interfaces are created dynamically on container startup. There are no ifcfg-* files to put NM_CONTROLLED=no into.
Can you attach NetworkManager logs? You can setup NetworkManager.conf not to create default connections for eth devices (man NetworkManager.conf): [main] no-auto-default=*
Created attachment 932584 [details] NM logs Hi, I've started NM, started the LXC container, and shut NM few seconds later.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.