Sonic <sonicsm...@gmail.com> 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.
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. > 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. You didn't include any pieces of your pf.conf to show, so who can judge? Anyways I'll let other people you didn't show your config to explain how you are probably using pf incorrectly on interfaces configured with dynamic addressing. > Almost, because my supersedes, etc. in /etc/dhclient.conf are > completely ignored. Of course. > The only workaround I found was to disable resolvd so I could manually > propagate /etc/resolv.conf without it being overwritten. We take no position on what people do after they install openbsd...
