Christian Weisgerber <na...@mips.inka.de> wrote: > Peter J. Philipp: > > > Would OpenBSD be interested in a daemon that gets nameserver information > > from > > pppoe0 and passes this nameserver information to resolvd(8)? Currently > > there > > is no way to do that, so a userland daemon that uses a bpf device to spy on > > pppoe(4) may be worthwhile to write? Is this overcomplicating things? > > Too complicated. Quoting from resolvd.8: > resolvd also monitors the routing socket for proposals learned > by dhclient(8), dhcpleased(8), slaacd(8), or network devices which > natively learn DNS information such as umb(4). > > I think pppoe(4)--well, sppp(4) actually--needs to learn the > nameserver information and send it to the routing socket. umb(4) > should provide a template.
Precisely. That's the whole idea -- that any new kind of DNS-aware network can submit routing socket proposals -- either from userland as slaacd/dhcpleased do, or from the kernel as umb(4) does now -- and resolved will using a sorting algorithm to place the DNS address into resolv.conf It is even better if the subsystem can submit offer withdraws when they go down, so that the resolv.conf file can get updated again. So if it wants to do withdraws, it must be integrated into the ppp code correctly.
