Cluster VPN with 2 server nodes

[tonypd]

Hi everyone,

I set up 2 VPN servers with the latest version compiled from GitHub, version 4.43 Build 9799, on AlmaLinux 8.9 amd64.

1 as a controller member
1 as a cluster member

Both manage all VPN client sessions.

I read the documentation and maybe I missed something. If I reboot the cluster member, the VPN clients are disconnected and when they reconnect, they can connect to the controller. The cluster controller would be fine. However, if I reboot the controller member, all VPN clients lose connection, including the cluster member.

My question is: Is this behavior by design? Or is there any configuration I am missing to manage the client connections when a node (controller or member) must be rebooted for some reason, to avoid losing all connections?

If such a configuration exists in the documentation, I would appreciate it if you could point me to it, as I couldn't find how it works in this case.

I expected high availability (HA) sessions to be available when one of the servers is rebooted, in maintenance mode, or while upgrading the version, to manage all VPN client sessions on the other server. Otherwise, I have to convert both into standalone to avoid this issue if the controller has a big problem and can't connect with the other VPN servers.

Is there an option to automatically set the cluster member as standalone if something happens, or to manage all connections without disconnecting while the controller is rebooting or recovering?

Is this behavior by design?

Thank you.

[cramaboule]

Hello,

the documentation is here: https://www.softether.org/4-docs/1-manual/A/10.8
But I face the same problem with preliminary tests. Client get disconnect when server reboot.

C.