Hi,
I confirm that dhclient don't read(apply) /etc/dhclient.conf configuration
beginning from 6.9am64 and set in /etc/resolv.conf ISP search domain and
nameserver(s) even without any complex setup in name resolution:
$ cat /etc/resolv.conf
search domain.name
nameserver ISP.nameserver
nameserver 127.0.0.1
lookup file bind
$ cat /etc/dhclient.conf
timeout 30;
retry 1;
reboot 3;
select-timeout 0;
backoff-cutoff 2;
initial-interval 1;
interface "re1" {
send dhcpd-lease-time 3600;
supersede dhcp-server-identifier 255.255.255.255;
supersede domain-name-servers 127.0.0.1;
request
subnet-mask,
broadcast-address,
routers;
require
routers,
subnet-mask;
ignore
host-name,
domain-name,
domain-search,
domain-name-servers,
interface-mtu,
ntp-servers,
time-offset;
}
/etc/dhclient.conf explicitly set to ignore "domain-search,
domain-name-servers" from ISP but actually they both in first place of
/etc/resolv.conf and update every time once IP address is assigned.
>From my observations, the behavior of ignoring /etc/dhclient.conf parameters
>by dhclient appeared since 6.8amd64 was upgraded to 6.9amd64.
Hope this helps to find the issue.
Martin
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, July 17, 2021 1:57 AM, Sonic <[email protected]> wrote:
> Having some issues after a sysupgrade to the latest snapshot (of this
> writing) - OpenBSD 6.9-current (GENERIC.MP) #131.
>
> Seems the base change to dhcpleased/resolvd has presented some issues.
> Pf does not start on boot as it claims my dhcp interface has no
> address, however after logging in I can load pf and almost resume
> normal operations. Apparently the interface does get an IP address,
> but the start of pf doesn't wait for it.
> Almost, because my supersedes, etc. in /etc/dhclient.conf are
> completely ignored.
> The only workaround I found was to disable resolvd so I could manually
> propagate /etc/resolv.conf without it being overwritten.
