[FS#4169] dnsmasq init script not generating full config on boot

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Perry (pmelange) 

Attached to Project - OpenWrt/LEDE Project
Summary - dnsmasq init script not generating full config on boot
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - All
Due in Version - Undecided
Due Date - Undecided
Details - when using the "notinterface" option, the init script generates the config file /tmp/etc/dnsmasq.conf.cfgABCDEF without any "except-interface" directives.  The "interface" option is also likewise affected.

This is done only at boot time and not when dnsmasq is restarted.

The commit which introduced this is 2336b942b37f265c59547d738ca558b61102833d

Would it be better to perform a "ubus -t 15 wait_for network.interface.$X" to allow netifd to finish initializing before the dnsmasq config file is generated?

In order to test, do the following (assuming $DEV is the WAN device which has an IP address of $IPADDR):
* Add "list notinterface $DEV" to the dhcp config file
* reboot
* log back into router
* nslookup google.com $IPADDR
** Here there is a response from dnsmasq, even though the interface should be disabled
* /etc/init.d/dnsmasq restart
* nslookup google.com $IPADDR
** Here the result is as expected "connection timed out; no servers could be reached"



More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=4169

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.