Great, glad I could help.
I think I may have found a few more bugs in firmware 4.6.0 (snapshot brume 2)
When adguard is enabled (with / without adguard client handling enabled) and a wireguard client is running an error occurs - the error occurs when you reboot the router AFTER you have enabled the options I mentioned.
I notice in my logs that ddns records couldnt update and the plugins list wouldn't update in the GUI or via Luci. I found a busybox ns error and searching posts on here I found that it's was discovered there was some DNS issues at play, after some testing I turned off adguard home which then gives me the "DNS Server Settings" back inside the Glinet GUI, I switch between the modes so that the apply button becomes enabled and select the mode: "Automatic" and hit apply. Turn back on adguard and the Wireguard client and now I can pull the software updates in the GUI / Luci and the ddns works. I can replicate this error by rebooting and then doing the same "fix" So basically if adguard is enabled and wireguard client is enabled / running after rebooting the router you will find that the router itself can't then get DNS to perform the said tasks. * I am again using the policy based routing via client device, with the USE VPN option. I have tested without the VPN client and it works correctly so the key thing here is that you must be running the Wireguard client to replicate the bug.
^ there was a post reported similar to what I've mentioned above: 'opkg update' fails with custom DNS server set - #9 by Happi
2nd bug - When inside Luci and clicking restart firewall I noticed that ALL my clients (even ones that shouldnt be going via VPN) then get routed over the VPN and my policy based routing via devices (Use VPN) doesn't kick in. After restarting the firewall inside Luci I then need to head over to the Wireguard Client GUI, click on the "define by MAC address" to bring my list of clients up and hit apply again. Once done, I then visit ipleak test and see my NON routed clients again work over WAN and my policy based clients going back over VPN, so it would seem some kind of rule / check should be made if the firewall has restarted for whatever reason - I was installing a plugin that required a firewall restart which is when I then noticed that all clients appeared to then go over VPN regardless (wireguard client)
The 3rd bug is a DNS leak when using "Enable VPN Cascading " over a different network (LTE in this case)
With VPN Cascading enabled my DNS leak test reports the correct external VPN DNS and country VPN IP of my external wireguard client but it also reports the DNS that are used in my wireguard server / client config which appear to be going out over WAN and are coming from my clearnet country location NOT that of my VPN resulting in a DNS leak.
I hope that by reporting these bugs here and not creating another thread is okay, the bugs I've reported are all DNS related anyway so they still fit under the umbrella of this topic.
With that said, may I ask where I can post future bugs / suggestions? There doesn't seem to be many categories on the forum. I would have presumed there to have been a dedicated section for bug reporting or suggestions, firmware version(s) sub forum, sub forum categories for each released model of router (brume2 section) for example.