Topics

Hi, I don't know if this has been reported before.  I recently switched from ISC to dnsmasq and today noticed a plethora of log overflow errors, so I attempted to adjust the logging level.

Code Select Expand

2026-01-20T15:37:42-08:00 Warning dnsmasq overflow: 15 log entries lost
2026-01-20T15:37:42-08:00 Warning dnsmasq overflow: 4 log entries lost
2026-01-20T15:37:42-08:00 Warning dnsmasq overflow: 15 log entries lost
2026-01-20T15:09:39-08:00 Warning dnsmasq overflow: 9 log entries lost

I had enabled "Log DHCP options and tags" and was seeing those when viewing informational logs, so I disabled the option and saved settings.  However, the logging did not change.

It appears that no matter what log settings are selected in the configuration, the logging options in the dnsmasq.conf file do not change.  Other settings such as 'no-hosts' apply correctl.

/conf/config.xml fragment:

Code Select Expand

    <dhcp>
      <no_interface/>
      <fqdn>1</fqdn>
      <domain/>
      <local>1</local>
      <lease_max/>
      <authoritative>1</authoritative>
      <default_fw_rules>1</default_fw_rules>
      <reply_delay/>
      <enable_ra>1</enable_ra>
      <nosync>0</nosync>
      <log_dhcp>0</log_dhcp>
      <log_quiet>0</log_quiet>
    </dhcp>

Code fragment from the template /usr/local/opnsense/service/templates/OPNsense/Dnsmasq/dnsmasq.conf:

Code Select Expand

{% if dnsmasq.dhcp.log_dhcp %}
log-dhcp
{% endif %}
{% if dnsmasq.dhcp.log_quiet %}
quiet-dhcp
quiet-dhcp6
quiet-ra
quiet-tftp
{% endif %}
Template output from /usr/local/etc/dnsmasq.conf:

Code Select Expand

log-dhcp
quiet-dhcp
quiet-dhcp6
quiet-ra
quiet-tftp


After updating to OPNsense 22.7.5 zenarmor is refusing to start the packet engine service.

I receive the following dialog after trying to start it manually:

Code Select Expand

Warning: zenarmor is stopped because of a problem

zenarmor has detected a problem during operation and has shut down zenarmor services in order to prevent a network outage.

It is highly probable that this is due to a netmap issue where netmap might not be inter-operable with your current ethernet adapter.

If you think this is something we should have a look, just click here to let us know about the details and we will investigate this further.

You can re-enable the services from Status page.


I also receive an email notification with the following:

Code Select Expand

Time Priority Category Firewall Title Message
2022-10-05 21:45:25 UTC crit service ([REDACTED]) Engine service error Failed initializing network interfaces

I've reported this to Sunnyvalley also.