DDNS and VPN client conflict?

[MrCfrhk]

I’ve enabled the VPN client service on my Slate AX(v4.1.0).
Also, I’ve enabled the DDNS service at the same time.
However, the DDNS service cannot get the correct public IP address.
It’s always mapped to my VPN IP even I’ve enabled the “Services from GL.iNet don’t Use VPN” option.

How can I fix it?

[MrCfrhk]

Update: I’ve sloved it by disable “Services from GL.iNet don’t Use VPN” option and re-enable it.
But after I reboot the router, it’s will get VPN IP again.
I think this is a bug for the router firmware…

[Almahadeus]

Longstanding bug reported by me and others on these fora but another one of those serious issues with these routers that go unresolved.

[MrCfrhk]

Could you tell me what’s the another one serious issue?

[Almahadeus]

Here is an example:

AXT1800's 5GHz SSID disappears as soon as device is repeating another 5GHz signal

That is really bizarre as I have tried it again and the repeater is connected successfully. I have been waiting for more than 30 minutes now and the AXT’s 5GHz is not showing up when scanning on any of my WiFi clients (PC, mobile…etc.). Does it make a difference if I am repeating a DFS channel? I will try a non-DFS one and report back (I love the “Allow Repeat DFS Channels” feature by the way). [2022-05-23_093102]

I have started to slowly give up on GL.iNET ironing these important issues out before dishing out new models with partially baked firmware versions all the time. I am looking to go back to Asus as my main router at home now that they support wireguard.

[MrCfrhk]

I was planned to buy their new Beryl AX to bring to the office as a VPN AP util I found their products are so buggy…