The system works correctly, the GL-iNet connect to the VPN server, it allows the navigation to the LAN connected device through WAN, VPN, and LAN. Also through WiFi, I can access to the GL-iNet interface to it’s IP 172.16.0.254 and to the LAN connected devices typing 172.16.0.1.
I’m also able to open the LAN device interface directly from the OpenVPN server.
The problem is that randomly, the GL-iNet become not available through the OpenVPN direct IP access (when I type on the browser the GL-iNET OpenVPN IP address or if I try to connect through ssh to the OpenVPN IP address).
The GL-iNet remains unavailable for a couple of minutes.
If I try to connect to the LAN device from the OpenVPN server, the connection will be unlocked and I can connect again typing the GL-iNet OpenVPN IP address.
The GL-iNet (OpenVPN client) connec to to the OpenVPN server.
The GL-iNet receive it’s IP i.e. 10.210.0.11
I ping the GL-iNet IP 10.210.0.11 from the server or from other VPN clients and the GL-iNet ping answer without interruptions.
No, the VPN is not lost.
The GL-iNet answer to PING inside the VPN so it is not lost.
Even if it answer to PING, I’m not able to SSH into GL-iNet from VPN but only through LAN or WiFi.
If I interrogate the GL-iNet from the OpenVPN server, the GL-iNet I can connect in SSH inside the OpenVPN net.
This random blocks stops only when I interrogate the GL-iNet from the OpenVPN server.
Also, this strange problem appear only with the GL-iNet and not with other VPN clients we use.