VPN client only works on WAN1

[Luana]

We configured failover, and when WAN1 goes down, WAN2 doesn't work on the VPN client, even when using DDNS in the VPN configuration.

[alemabrahao]

If you have both WANs activated, the VPN client will only work for the WAN that you have configured as primary, not for both at the same time. Because in case of failure, the working WAN will take over.

[Luana]

Hi, 🙂 but the problem is that when WAN1 fails, WAN2 becomes the primary connection, and the VPN client doesn't work. It only starts working again when WAN1 re-establishes the connection.

[Mloraditch]

Is the DDNS updating? if not, contact support

If the DDNS is updating, there could  be some sort of ISP issue, especially if you are using the older client vpn. What is your secondary ISP? Do you have public ips from them?

[alemabrahao]

Mas o cliente tem que desconectar e conectar novamente para reestabelecer a conexão, você chegou a fazer esse teste?

[PhilipDAth]

When WAN1 fails, the appliance will send a DDNS update so that the DNS entry points to the IP address of WAN2.  The DNS update can take up to 10 minutes.  Typically it takes around 5 minutes.

[GIdenJoe]

Indeed, only the primary configured WAN is listening for the Client VPN sessions.
It does take some time for the DDNS to update.

You can however test this when doing an nslookup how long it takes for your to get the other IP address.
You can also test the absolute WAN addresses by checking dynamicname-1 or dynamicname-2.dynamic-m.com