aboutsummaryrefslogtreecommitdiffstats
path: root/package/firmware
diff options
context:
space:
mode:
authorYousong Zhou <yszhou4tech@gmail.com>2019-02-18 14:11:19 +0000
committerYousong Zhou <yszhou4tech@gmail.com>2019-02-24 01:55:47 +0000
commit87fb8aea877b39f13a18df71df00522e13395004 (patch)
tree268789fc4dc3ddaa1951879e72f6247505c4a1e7 /package/firmware
parent405840631c87d7d5c3381e82d61504b318c8a555 (diff)
downloadupstream-87fb8aea877b39f13a18df71df00522e13395004.tar.gz
upstream-87fb8aea877b39f13a18df71df00522e13395004.tar.bz2
upstream-87fb8aea877b39f13a18df71df00522e13395004.zip
dnsmasq: allow using dnsmasq as the sole resolver
Currently it seems impossible to configure /etc/config/dhcp to achieve the following use case - run dnsmasq with no-resolv - re-generate /etc/resolv.conf with "nameserver 127.0.0.1" Before this change, we have to set resolvfile to /tmp/resolv.conf.auto to achive the 2nd effect above, but setting resolvfile requires noresolv being false. A new boolean option "localuse" is added to indicate that we intend to use dnsmasq as the local dns resolver. It's false by default and to align with old behaviour it will be true automatically if resolvfile is set to /tmp/resolv.conf.auto (cherry picked from 2aea1ada65f050d74a064e74466bbe4e8d) Tested-by: Paul Oranje <por@oranjevos.nl> Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> Acked-by: Hans Dedecker <dedeckeh@gmail.com> Acked-by: Paul Oranje <por@oranjevos.nl>
Diffstat (limited to 'package/firmware')
0 files changed, 0 insertions, 0 deletions