You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When dnsmasq's init script is invoked via the boot process, the UCI config option add_wan_fqdn is no longer effective. The content of /tmp/hosts/dhcp. only contains: # auto-generated config file from /etc/config/dhcp
If dnsmasq is restarted after the network is up, it works as expected.
This is caused by commit [[https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=ecd954d5302b2d135005ca68c206bb2d544b0bde|ecd954d5302b2d135005ca68c206bb2d544b0bde]], which adds some conditions to the service triggers, one being the ignore option must be disabled.
The add_wan_fqdn option only takes effect when the ignore option is enabled.
The commit message suggests the condition was added in reverse:
//if the value of the ignore option is set to 0, then the corresponding interface trigger is not installed. Otherwise, if the ignore option value is 1, then procd_add_interface_trigger is called which adds the interface trigger.//
I've confirmed that reversing the condition fixes the problem, and have attached a patch for this.
The text was updated successfully, but these errors were encountered:
philsauce:
When dnsmasq's init script is invoked via the boot process, the UCI config option add_wan_fqdn is no longer effective. The content of /tmp/hosts/dhcp. only contains:
# auto-generated config file from /etc/config/dhcp
If dnsmasq is restarted after the network is up, it works as expected.
This is caused by commit [[https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=ecd954d5302b2d135005ca68c206bb2d544b0bde|ecd954d5302b2d135005ca68c206bb2d544b0bde]], which adds some conditions to the service triggers, one being the ignore option must be disabled.
The add_wan_fqdn option only takes effect when the ignore option is enabled.
The commit message suggests the condition was added in reverse:
//if the value of the ignore option is set to 0, then the corresponding interface trigger is not installed. Otherwise, if the ignore option value is 1, then procd_add_interface_trigger is called which adds the interface trigger.//
I've confirmed that reversing the condition fixes the problem, and have attached a patch for this.
The text was updated successfully, but these errors were encountered: