[Possible bug] Berl AX doesn't attempt to connect to the second OpenVPN server when the first one is down

Context
To create high availability, I have two OpenVPN VPN servers (not GLI routers) on separate computers. One server runs on port 1194, and the other on port 1195. I am using a Beryl AX as a VPN client to connect to the VPN servers.

On my VPN client configuration, I have an entry for each server:

remote <address of the server> 1194
remote <address of the server> 1195
connect-retry 10
connect-retry-max 0
resolv-retry infinite

Problem
If my first server is down (the one that is running on port 1194), Beryl AX doesn't try to connect to the second server and it just show an error message saying that the server is down

daemon.notice netifd: Interface 'ovpnclient' is now down
user.notice firewall: Reloading firewall due to ifdown of ovpnclient ()

Using the OpenVPN client app works
If I use the same VPN Client configuration on the OpenVPN client app for Mac, it works. It understands that the first server is down and then connects to the second one.

How do I make GLInet connect to the second server if the first one is down? It seems to be a bug.

Hi,

Regarding the OpenVPN client support mutil-server in the GL router, this feature has submitted in the firmware plan, still in the developing. Now the firmware version has not supported mutil-server and failover automatically in the OpenVPN client. Kindly await.

2 Likes