On 4/12/23 20:20, Theo de Raadt wrote:
Stuart Henderson <stu.li...@spacehopper.org> wrote:
On 2023-04-11, Theo de Raadt <dera...@openbsd.org> wrote:
Kaya Saman <kayasa...@gmail.com> wrote:
This somehow is overriding my resolv.conf file; another words the
information is *not* being used from resolv.conf and is instead being
used from the ipcp negotiation as part of the pppoe kernel module.
then the pppoe code should submit a RTM_PROPOSAL route message ...
it does.
i still don't see how this information can *override* resolv.conf
But I do not understand what "override" means. resolvd intentionally
has NO MECHANISM to allow choice, the list of addresses is chosen by a
fixed internal heuristic, INTENTIONALLY without configuration knobs.
There is one knob: If one doesn't want resolvd semantics, stop the
daemon. So easy. But by default, the system runs with it, because
that means 99% of users get the semantics which satisfy 99% of
users without having to handle a configuration file.
What I don't understand from the complaint is why that ppooe dynamic
address doesn't rise to the top of the file, because dynamic requests
of that kind always rise to the top. Therefore they get used.
So if it isn't in the file, then something else has been broken, probably
by the user, right?
But it is probably best to ignore this entire discussion because some
piece of configuration has been done to BREAK the default behaviour,
and then the user owns all the pieces.
Hi Theo, I apologize if it sounded like a complaint?? It was not meant
to be..... honestly.
Like I mentioned previously, it may have had something to do with me
running: sh /etc/netstart pppoe0 a few times after the system had been
booted. I was at the time trying to make use of 2 isp's and route
accordingly per subnet or even ip address. It might have even been
triggered by my altering of the pf.conf file... they are the only two
things that I have been touching.
What I meant by *override* is that the default behavior that I had set
the machine up for was not being seen. The information which I have
input into /etc/resolv.conf has not changed for years.
I accept maybe i fiddled with things and caused unwanted behavior... it
can happen.
All I was trying to figure out is why the resolv.conf file was not being
used and instead the information obtained through ipcp was being used
for dns lookups. If I had caused it that's fine but I didn't understand
what I did to have caused it and was just seeking help and advice that
maybe someone might suggest things to try.
But as it is, the system is back to how I want it to be so for sure
please feel free to ignore the thread. There is no more problem ;-)
Thanks for chiming in by the way, it is appreciated.
Potentially, would it be a good idea to have setting to disable the dns
or other information obtained by ipcp within the kernel ppp codeset? I
just might be in the minority here so please feel free to ignore it's
fine, I'm just thinking out loud....
Regards,
Kaya
