DNS/Connection/NAT Problems since 24.1.8

[drdownload]

I have set my OPNsense installations to auto-update. yesterday 24.1.8 broke connectivity on my 24+ months updated systems.

It doesnt seem to be one single behaviour/option that is the issue:

I have on  all locations (private) double NAT setups, all connected with wireguard side to side vpn and using an openvpn tunnel for some asn.

all was working fine. buuuut then i started to pull my hair out.

dns was blocked, ping was blocked, unbound not responding.

it worked on and off playing with options like "dont use local nameserver", but stopped without changing options.

I noticed that the WAN IP was set to a /32 subnet (and therefore i couldnt reach the Modem), changed that to 24.

I noticed that it started working if i set the bogus and private adresses block on the WAN interface (how?) and it stopped everytime I restarted the openvpn tunnel.

Right now it works as long the openvpn tunnel is running, but it shouldnt route tru this tunnel (only 2 ASN)

[drdownload]

after every reboot DNS doent work, only after changeing and saving something on the wan interface.

[longtom]

Thanks for your Thread, i have the same issue with NAT and DHCP server over 3rd Party Wireguard tunnel.
Is there any report to opnsense?