On Mon, Aug 3, 2015 at 8:30 AM, <gottl...@nyu.edu> wrote: > > On Sun, Aug 02 2015, Canek Peláez Valdés wrote: > > > On Sun, Aug 2, 2015 at 10:03 AM, walt <w41...@gmail.com> wrote: > >> > >> I've been running systemd for a long time without needing to enable > >> the dhcpcd service at boot time. Starting with systemd-224 that is no > >> longer true. Today I had to enable dhcpcd.service specifically or the > >> network interface didn't get an ip address during boot. > >> > >> Seems like this might be especially important for those of you who need > >> to update remote machines. > > > > If you enable systemd-networkd.service, and your .network file has DHCP=yes > > in its [Network] section, then it will use the DHCP client included with > > systemd-networkd. > > > > In my servers I not longer use any net-misc/*dhcp* package. > > > > Regards. > > Is this server-related? I have only simple workstations/laptops and I > don't enable systemd-networkd at all. It seems that NetworkManager > takes care of both wired and wireless without assistance (including > dhcp).
In latptops/workstations NetworkManager takes care of everything. However, I still enable systemd-networkd and systemd-resolved in my laptop and workstations. If enabled without any configuration, it just monitors the network interfaces and keeps them "in the loop" for the rest of the system to know about them from a central registry. It doesn't interfere with NetworkManager (or any other network management program for that matter). It's not mandatory to enable them either. However, there were advantages to doing so; for example, in my laptop, systemd-timesyncd would try to sync the clock only if there was a network connection available. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
