gwes <g...@oat.com> wrote:
> On 7/16/21 10:35 PM, Theo de Raadt wrote:
> > This is intentional.
> >
> > We are moving from a model where dhclient on 1 interface believes it is
> > MASTER of /etc/resolv.conf and a bunch of system aspects, and the
> > userbase is familiar with a pile of hacky control knobs in
> > dhclient.conf.
> >
> > Towards a model where multiple interfaces + unwind can advertise their
> > DNS resolution abilities to resolvd, which then sorts the offers and
> > maintains a configuration.
> >
> > dhclient will remain available for people who want that old model, but I
> > suspect they will encounter increasing difficulty sticking to it.
> >
> > Because the default configuration is changing.
> >
> >
> dhcpleased inspects all interfaces
Bullshit.
> dhclient only works with assigned interfaces
> There are times when one interface configured by dhcp must be supervised
> but other interfaces must not be disturbed >>despite any flags<<,
> e.g. during
> a reconfiguration, testing, switchover, etc.
> Will there be a way to confine dhcpleased to a defined set of interfaces?
dhcpleased only works on interfaces configured "inet autoconf".
dhcpleased is a dynamic host configuration protocol (DHCP) daemon for
clients. It requests IP configuration information from for example those
offered by dhcpd(8), on interfaces with the AUTOCONF4 flag set.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Is there a way to confine slaacd to a defined set of interfaces? Yes.
Exactly the same way.
slaacd is a stateless address autoconfiguration (SLAAC) daemon for
clients. It listens for IPv6 router advertisement messages, for example
those sent by rad(8), on interfaces with the AUTOCONF6 flag set.
