After upgrade 25.1.5_5 -> 25.1.6_4 we noticed that Dnsmasq now tries to load /usr/local/etc/dnsmasq.conf.d/* while previously it loaded only *.conf
If there are files it cannot parse in this folder, Dnsmasq service fails to start.
I am not sure if it is an intentional change as /usr/local/etc/dnsmasq.conf.d/README still talks about .conf files:
# Dnsmasq plugin directory:
# Add your *.conf files here, read in alphabetical order
Quote from: xofer on May 13, 2025, 11:35:39 AMAfter upgrade 25.1.5_5 -> 25.1.6_4 we noticed that Dnsmasq now tries to load /usr/local/etc/dnsmasq.conf.d/* while previously it loaded only *.conf
If there are files it cannot parse in this folder, Dnsmasq service fails to start.
I am not sure if it is an intentional change as /usr/local/etc/dnsmasq.conf.d/README still talks about .conf files:
# Dnsmasq plugin directory:
# Add your *.conf files here, read in alphabetical order
Yes, this is a bug and did not exist prior to 25.1.6 release.
Best is to raise this on Github... so that it can hopefully be fixed in next iteration
This maybe?
# opnsense-patch https://github.com/opnsense/core/commit/4b0b3bf9f5
(reapply dnsmasq configuration to take effect)
Cheers,
Franco