Hi,
So I'm fiddling around with the new vpn dashboard on my MT3000.
To my surprise I noticed a bottleneck and I'm not so sure if I'm doing it right or wrong. 
So I added a local wireguard client, and ensured the DNS section has been specified to 10.6.7.1, this will ignore GL dns settings but that is my intention, I base this of the pre configurated mullvad configs.
Of course this wil not give me internet to the dns, because in the older firmware I had to check:
But after this change I see that every try to dns has been dropped, this is unexpected because the expected behaviour should be that lan access was allowed, is this a bug?
Anyway, as soon when I change the global proxy to policies and use 10.6.7.1 to bypass to wan it works fine.
Now I haven't tested this on a external other network, so maybe something masquarading related with inner zones on my main router blocks it although I doubt this since bypassing the tunnel on the MT3000 magicly worked in the end it is just a route, but I found this confusing, this was not previously before the dashboard change.
The config in my MT3000:
[Interface]
Address = 10.6.7.2/32
PrivateKey = snip
DNS = 10.6.7.1
MTU = 1420
[Peer]
AllowedIPs = 0.0.0.0/0
Endpoint = snip.ddns.net:4443
PersistentKeepalive = 25
PublicKey = snip
Edit
Just tested the direct config on my phone connected to the MT3000, I see no issue, something in the gl kill switch is blocking it.
The firmware is:
4.8.0 release 3 (2025-07-23 12:47:20 (UTC+00:00))
Edit 2:
adding 10.6.7.1/32 to allowedips don't work either, neither on the server which then forces a route, I can however perfectly fine connect to 10.6.7.1 even without it defined in allowedips and reach the gateways web interface, but 53 traffic don't want to work, I'm 100% certain it must be a kill switch problem.
