Hi,
I am oldfashioned, I have been using Linux for over 20 years when we still had
to compile our own kernels to support certain hardware. :-(
I have always configured the network interface on my Linux machines via
/etc/network/interfaces and not via DHCP. The reason for that is quite simple,
most of my Linux machine ARE my DHCP servers. :-)
I never used the network manager as that is more work for me, I have no idea
how that works even. ;-)
My interfaces file pretty much always looks something like this. I barely ever
use the new option to use the /etc/network/interfaces.d/ path.
-=-=-=-=-=-=-
$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug ens32
iface ens32 inet static
address 172.16.208.19
netmask 255.255.255.0
gateway 172.16.208.1
-=-=-=-=-=-=-
All other servers DO use DHCP for their config and get a static ip number via
settings in the /etc/dhcp/dhcpd.conf file.
That way I can centrally manage the ip network config in case something
changes, like maybe the network mask when the number of devices grows beyond my
initial estimate. That has happened twice in the past 20 years.
For IPv6 configuration I still use the auto config from the router and not
DHCPv6. In IPv6 they looked good at what was missing from IPv4 and was
available in other protocols like IPX where you never did any configuration on
the client.
I have noticed that is the local dns server is properly configured everything
works by default.
Bonno Bloksma
