Yousong Zhou 87fb8aea87 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>		2019-02-24 01:55:47 +00:00
..
config	netifd: handle hotplug event socket errors	2019-02-02 20:48:32 +01:00
ipv6	map: drop default encaplimit value	2018-12-18 11:28:13 +01:00
services	dnsmasq: allow using dnsmasq as the sole resolver	2019-02-24 01:55:47 +00:00
utils	ethtool: update to 4.19	2018-12-18 17:22:09 +01:00