On Wed 10/11/2021 16:53, Sebastien Marie wrote: > On Wed, Nov 10, 2021 at 04:22:49PM +0100, Bjorn Ketelaars wrote: > > sppp(4) is currently using RTP_PROPOSAL_STATIC for sending DNS > > proposals, whereas all others sources, e.g. umb(4), are using a specific > > value. Diff below fixes this by adding RTP_PROPOSAL_PPP. > > > > Although the diff is limited in size it touches several pieces: > > - sppp(4) > > - route(4) > > - route(8) > > - unwindctl(8) > > > > Thanks to semarie@ for noting the above. Thanks to claudio@ for > > suggesting RTP_PROPOSAL_PPP. > > > > Comments/OK? > > ok semarie@ > > I just wonder about the system behaviour after building a new kernel > and rebooting to build userland: RTP_PROPOSAL_SOLICIT is changed and > kernel/userland will mismatch. > > But UMB proposal was done this way too (moving RTP_PROPOSAL_SOLICIT to > next id). So disturb shouldn't be big.
Yes, you are right, there is some disturbance. I should have written this in my mail. I did some testing before sending this diff, and what seems to happen with a kernel/userland mismatch is that DNS proposals from sppp(4) are not picked up by resolvd(8) and unwind(8) (unwindctl status autoconf does not mention these proposals). Other proposals, e.g. from dhcpleased(8), are ok. Behaviour is fixed after building userland and restarting resolvd(8) and unwind(8). Sorry for not mentioning this.
