4.0 and VPN policy

I have the same issue. If dns server is internal of vpn and vpn policies are active then no dns resolution.

It’s urgent to have a proper fix of this.
Thank you.

Is there any possible workaround?

The newest version is 4.0.1, you can have a try:
http://download.gl-inet.com/firmware/snapshots/20220808_4.0.1_release5/axt1800/

I think is still in beta, because it doesn’t appear on the web site still

There is no mention of thee resolution of this issue in the changelog https://forum.gl-inet.com/t/slate-ax-firmware-4-0-1-release-4-is-out/23313

I used Azirevpn and I don’t have this problem.

Which wireguard service are you using?

Do you mean when vpn policy is actived but vpn is turned off?

Or vpn policy is activated and vpn is also on?

The second one. My service is StrongVPN. Issue is present in Slate Plus too.

I used the smartphone app to configure strongvpn wireguard.

I used mac based policy and add my pc to use vpn or do not use vpn.

All works as expected and dns can be resolved.

What could be the possible reason?

I use vpn policies ip/domain and no dns resolution if dns servers are on vpn network, all is ok if I set an e ternai dns server.
On Slate ax and Slate plus, old or new kernel…

I take some time to study this issue and it does seems a bug.

Submitted internally.

2 Likes

Another issue on slate ax is that on router restart no dns resolution if vpn policies are active. I have to stop and start vpn policies to solve issue. Issue is present on old and new kernel. Slate plus is not affected.
My domain/ip list is very long…

Thanks

1 Like

Maybe the same problem. Will fix both.

1 Like

if ones uses adguard then he/she can/should define a custom dns server for a client using vpn as explained in the following post:

https://forum.gl-inet.com/t/slate-axt1800-openvpn-adguard-home/23173

Hi @alzhao. Do you have any updates on the issue?

Yes. Can you try the snapshot? It should have fixed that.

I mean 4.0.2
https://dl.gl-inet.com/?model=axt1800&type=beta

Great! I just tested it, and it’s working!

It’s working now!
Thanks