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
If multiple instances of dnsmasq are configured, then every instance has access to the DHCP host files of all other instances of dnsmasq.
For example, if two instances are configured in /etc/config/dhcp, "default" and "guest", then when they are started (or if they receive SIGHUP), then each instance will log something like this to syslog:
From /etc/init.d/dnsmasq it doesn't look like this is intentional, as procd_add_jail_mount() is called with the instance's own host file ($HOSTFILE) only.
The text was updated successfully, but these errors were encountered:
jefferyto:
If multiple instances of dnsmasq are configured, then every instance has access to the DHCP host files of all other instances of dnsmasq.
For example, if two instances are configured in /etc/config/dhcp, "default" and "guest", then when they are started (or if they receive SIGHUP), then each instance will log something like this to syslog:
Thu Feb 7 04:26:47 2019 daemon.info dnsmasq[3092]: read /tmp/hosts/odhcpd - 1 addresses Thu Feb 7 04:26:47 2019 daemon.info dnsmasq[3092]: read /tmp/hosts/dhcp.default - 2 addresses Thu Feb 7 04:26:47 2019 daemon.info dnsmasq[3092]: read /tmp/hosts/dhcp.guest - 2 addresses
From /etc/init.d/dnsmasq it doesn't look like this is intentional, as procd_add_jail_mount() is called with the instance's own host file ($HOSTFILE) only.
The text was updated successfully, but these errors were encountered: