I use it as a Wireguard VPN client (the VPN service I use is ProtonVPN). Typically, my client computer is connected to one of the LAN ethernet ports or to the router's Wi-Fi and the router is connected to internet either via the WAN ethernet port (ISP router) or via the USB port (tethering with a cellphone). No fancy settings otherwise (default DNS, DHCP, etc).
Either of these setups worked very well until recently. I suspect the late August update to have caused them to stop working properly.
More specifically, I notice 2 issues:
The biggest issue is that internet is unreachable (due to DNS unavailable?) from the clients connected to the router, even if itself is properly connected to the VPN server, as I can tell from the blue light turning white.
Could you please give me a hint about what I should investigate? Should I downgrade the firmware until I find a version that works? Should I check with my VPN provider that DNS is working properly? GL.iNet: is my issue already addressed in a forthcoming firmware update?
possible DNS service anomaly, please check if can ping 8.8.8.8 in SSH?
both setups (Internet source from cellphone and optical fiber) are not available?
please provide the syslog.
has ADH been enabled?
the network at the current topology, if is it available on a PC which using the same VPN profile as Slate Plus (from ProtonVPN)?
“-3 , the online upgrade is abnormal.” it could be that the device has no internet and the updates check fails because of the above issues, so let us check the above issues first.
I understand you ask for a test of the VPN connection skipping the Slate Plus altogether: using my cellphone (ProtonVPN app on Android), data plan and same Wireguard configuration, I access internet without issues (NB: I also own a Mudi V2 with the same Wireguard / ProtonVPN configuration and comparable setup without any comparable issues)
OK
While looking at the syslog, I noticed that the router's date and time are totally off: today is 21 November 2024, whereas http://192.168.8.1/#/timezone claims it is 15 October 2024! Perhaps the router does not reach the time server, just like it does not reach the firmware upgrade server (6.). I wonder how it is possible then that it manages to connect to ProtonVPN's servers. Maybe the time server and firmware upgrade server have a domain name therefore cannot be reached without DNS, whereas Wireguard configuration is based on IP addresses therefore allowing VPN connection without DNS. But then, why can't I ping 8.8.8.8 (1.)?
When disabled VPN, also failed to ping 8.8.8.8, please check the Internet issue of your Slate Plus WAN first:
I checked the syslog you posted, the WAN obtained the IP from primary ISP router, seems is normal, probably the issue is in the firewall rule, or NAT, or routing.