On Mon, Jul 19, 2021 at 01:42:41PM +0200, Christian Weisgerber wrote:
| Look guys, it's simple.
|
| If you want IPv6 (SLAAC) autoconfiguration, you set "inet6 autoconf"
| for that interface. slaacd(8) will then automatically handle things.
|
| If you want IPv4 (DHCP) autoconfiguration, you set "inet autoconf"
| for that interface. dhcpleased(8) will then automatically handle
| things. If you require special DHCP options that dhcpleased(8)
| doesn't include, then you don't enable autoconfigurarion and run
| dhclient(8) instead, which can be extensively configured.
|
| Both slaacd(8) and dhcpleased(8) pass nameserver information to
| resolvd(8), which adds those nameservers to /etc/resolv.conf unless
| unwind(8) is running. If you don't want that to happen for some
| other reason, you turn off resolvd(8).
One thing of note though, is the fact that dhcpleased does its work in
the background. This means that other services will start before you
get a lease. In the past, dhclient(8) ran in the foreground, trying
to get a lease until some timeout expired. *Usually*, that timeout
didn't trigger (at least, in my use cases).
So far, I've found NFS and syslogd to need configuration changes or
/etc/hosts entries to ensure they start properly. One could argue
that in these cases, one shouldn't use DHCP and just use statically
configured addresses (especially in the case of syslog, where you lose
messages when the service starts before an address is configured, even
with your remote syslog host added to /etc/hosts)
Cheers,
Paul 'WEiRD' de Weerd
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
