Hey, so as part of the discussion about NetworkManager vs systemd-networkd,
one thing that happened is networkd started exposing its DHCP code as
a shared library, and NetworkManager learned to use it if one specifies


in /etc/NetworkManager/NetworkManager.conf.  I have an open PR
to start doing this for Atomic Host:


However, we still have to lug around the RPM because of the
hard Requires in NetworkManager.spec:


Since at the moment, Fedora editions come from the same pool
of binary RPMs, we don't have a real mechanism for me to ignore
that dependency just for Atomic Host.

And anyways, I don't see a reason not to do this across the board,
hence this thread.

The networkd DHCP code has gotten a fair amount of testing
in server environments, but I suspect it could use more battle
testing in two things:

1) Desktop systems with a wider variety of DHCP environments (from
  home routers, enterprise environments with unusual DHCP servers)
2) Cases where one wants to propagate various config options
  from the DHCP server; see e.g. 

Anyways, let's get some more testing of this; if you have a few minutes
and you feel your DHCP situation is unusual, try frobbing the config option,
and report any failures in https://bugzilla.redhat.com/show_bug.cgi?id=1204226

If things seem OK I can do a Change page.
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Reply via email to