diff options
author | Yousong Zhou <yszhou4tech@gmail.com> | 2019-05-25 09:58:18 +0000 |
---|---|---|
committer | Yousong Zhou <yszhou4tech@gmail.com> | 2019-06-09 08:17:52 +0000 |
commit | 0299a4b73e729504dfdc5c4563535db082bdf941 (patch) | |
tree | 6659df0915e002fb92c75451275f0faa56c938d9 /rules.mk | |
parent | 6b762dd75fd2f9c22561a4fc8da29635be75cf8b (diff) | |
download | upstream-0299a4b73e729504dfdc5c4563535db082bdf941.tar.gz upstream-0299a4b73e729504dfdc5c4563535db082bdf941.tar.bz2 upstream-0299a4b73e729504dfdc5c4563535db082bdf941.zip |
dnsmasq: skip options that are not compiled in
This is to make life easier for users with customized build of
dnsmasq-full variant. Currently dnsmasq config generated by current
service script will be rejected by dnsmasq build lacking DHCP feature
- Options like --dhcp-leasefile have default values. Deleting them
from uci config or setting them to empty value will make them take on
default value in the end
- Options like --dhcp-broadcast are output unconditionally
Tackle this by
- Check availablility of features from output of "dnsmasq --version"
- Make a list of options guarded by HAVE_xx macros in src/options.c of
dnsmasq source code
- Ignore these options in xappend()
Two things to note in this implementation
- The option list is not exhaustive. Supposedly only those options that
may cause dnsmasq to reject with "unsupported option (check that
dnsmasq was compiled with DHCP/TFTP/DNSSEC/DBus support)" are taken
into account here
- This provides a way out but users' cooperation is still needed. E.g.
option dnssec needs to be turned off, otherwise the service script
will try to add --conf-file pointing to dnssec specific anchor file
which dnsmasq lacking dnssec support will reject
Resolves FS#2281
Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
Diffstat (limited to 'rules.mk')
0 files changed, 0 insertions, 0 deletions