[Buildroot] [PATCH] pppd: Do not overwrite /etc/resolv.conf
Jeroen Roovers
jer at airfi.aero
Mon Sep 11 07:58:21 UTC 2017
On 28 August 2017 at 22:28, Arnout Vandecappelle <arnout at mind.be> wrote:
>> pppd will overwrite any existing entries when /etc/resolv.conf is used instead, which is
>> bad.
>
> I agree that this is bad.
Thanks.
> However, this is a regression.
1. dnsmasq(8) mentions using /etc/dhcp/resolv.conf as well as
/etc/ppp/resolv.conf.
2. On the greater Internet you can easily find plenty of examples of
people getting confused because /etc/resolv.conf does not reflect what
usepeerdns has written to the wrong file in /etc/ppp/
3. usepeerdns is not enable by default.
> People who currently have ppp as their only
> interface, or who never have ppp and ethernet running at the same time
So it's a regression for what I can only assume must be a tiny
minority of system builders who don't configure their own systems and
are powerless but to rely on a second-guessed set of defaults that you
would like to support.
Additionally, the current pppd.mk suggests /etc/ppp/resolv.conf is not
writeable (in some configurations) but you say adding an ip-up script
would solve the issue, when that ip-up script is then supposed to
write to /etc/resolv.conf, which supposedly *is* writeable.
Please enlighten me.
Kind regards,
jer
More information about the buildroot
mailing list