Bump. Also update to 4.6.6. didnt solve it. You totally broke the router with the update of 4.6.4.
OpenVPN cant connect anymore, if you have Adguard Home enabled plus option "block non vpn traffic" enabled. Adguard Home doesnt resolve if OpenVPN is down.
Another bug I noticed with DNS on "automatic":
It claims DNS from OpenVPN is 10.0.0.243 which is totally wrong. OpenVPN has a totally diferent subnet. And 10.0.0.x is WG subnet.
I have the same configuration on a Brume 2 with 4.6.6. also with Adguard, and there it works fine, except I use Wireguard there, and on the Flint OpenVPN.
You broke Adguard Home DNS resolution with 4.6.4, so it wont resolve the initiation dns name of the OpenVPN name, and OpenVPN wont connect, and then also Adguard wont work. Disable Adguard and OpenVPN will resolve and connect.
Found a workaround to change the server name of the OpenVPN server in the OpenVPN config file from 87-1-de.cg-dialup.net to 181.214.173.196, and now it will connect again and then also vice versa Adguard will work too.
This obviously is just for clients behind the router, not the router itself. How would the router connect to the VPN, if it wont even resolve the VPN DNS in the first place. This worked in the past before 4.6.4, and it also works on Brume 2 with 4.6.6 with WG.
On Brume 2 this works totally fine with 4.6.6 but with Wireguard, there it also uses a name de966.nordvpn.com no IP and resolves it fine to initial connect.
Obviously Adguard needs to be excluded from the Block Non-VPN traffic, or the resolve of the OpenVPN server name and be resolved. Adguard is a service on the router itself, it is not a client.