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 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.
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"
The text was updated successfully, but these errors were encountered:
pmelange:
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 2336b94
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):
** Here there is a response from dnsmasq, even though the interface should be disabled
** Here the result is as expected "connection timed out; no servers could be reached"
The text was updated successfully, but these errors were encountered: