OPNsense 22.1.1_3 Upgrade to 22.1.2 - UNBOUND 100% CPU - Recovery needed

[devhunter55]

hm ..it seems it's related to :

https://forum.opnsense.org/index.php?topic=27299.0

@Franco mentioned (thx for that): "Every one of those creates a host route if you select a gateway for it. If these host routes conflict with the use in the gateway monitoring (most of the time because at least one host route overlaps multiple interfaces or the whole config is reversed there) you get the gateway flapping when the wrong interface comes back as the monitor uses the wrong gateway to monitor another."

So .. i did follow this recommendation - (setting the DNS Server Interfaces all to "none" ) - at least opnsense dns is (still) running without issues (did not do the upgrade yet again)

[keropiko]

Correct. I noticed that using the same dns ( for multiwan setup in settings-general) ip for gateway as well as monitor ip, when i "saved" the general-settings the monitoring stopped working. So i changed the dns to different ip's than the monitor ones. But i still have dns problems with unbound upon startup. I will try setting to "none"

[Davesworld]

Correct. I noticed that using the same dns ( for multiwan setup in settings-general) ip for gateway as well as monitor ip, when i "saved" the general-settings the monitoring stopped working. So i changed the dns to different ip's than the monitor ones. But i still have dns problems with unbound upon startup. I will try setting to "none"

I thought that if you have multiple wans with their own gateways that they do in fact, have to have a gateway set for each dns entry.

[vionsur]

These errors seem to be to do with setting up or renewing the public ip on the wan, so it might need a different diagnostic.