Messages

I have done the workaround many have suggested to cure the flapping, by putting a switch between the modem & the OPNSense box. And I have another modem on the way to see if that really fixes it rather than works around it.

So right now I can't test this (because I can't afford to degrade the system for testing's sake).

For the record, I did not reboot OPNSense after changing Unbound to listen on All. I will definitely try that if this problem rears its head again.

Also for the record:

OPNsense 26.1.8_5-amd64

It's an AppNeta m70, & it has 2 Intel I211 1GbE ports with igb drivers, & 4 Intel X553 1GbE with ix drivers.

The original connection was Ethernet cable directly between modem & one of the X553 ports. Then tried putting the WAN port on other of the X553, then on each of the I211 ports. No luck there. Currently there is un unmanaged switch between the modem & the OPNSense, which has cured the flapping & also the Unbound restarts.

The only clues in the General log were the Ethernet reconnection up/down events (flapping) which corresponded with the Unbound restarts in the Unbound logs. When those went away, so did the Unbound restarts.

My Unbound is restarting frequently, even every 15 seconds under heavy load. This is being caused--I believe--by my WAN interface flapping. That is a separate issue I am trying furiously to resolve, but in the meantime I am trying to get Unbound not to restart with every WAN flap.

I have seen in previous forum posts that this can be caused by having DHCP registration enabled in Unbound. I do not have it enabled. I have also seen that it can be caused by having specific interfaces specified for Unbound to listen on. I did have this set, but on seeing the recommendation to use the recommended setting of 'all' (no specific interfaces set), I configured it that way. But the problem persists.

Any other ideas why Unbound is repeatedly restarting?

With the option in Q-Feeds 'Register domain feeds' enabled

Well, if you explicitly enable the "block via Q-Feeds" feature, what do you expect?

I expected it to obey Unbound whitelists configured in Unbound, since it is using Unbound to do the blocking. It doesn't. But now an option has been added to remedy this, & you can set whitelists in Q-Feeds. With this formerly missing option, the problem was resolved for me.

In my case I found that the Q-Feeds Connect add-on was causing this. With the option in Q-Feeds 'Register domain feeds' enabled, it puts a blacklist file at /usr/local/etc/unbound/qfeeds-blocklists.conf . Even with Unbound blacklists turned off, this file remains & keeps blocking. Unbound whitelists don't affect it, & there appears to be no way to whitelist in Q-Feeds.