Depending on the VPN type and the resources type, you must use the correct remote access client. For SSL VPN, this is either CudaLaunch or a browser, depending on the resource. For full client-to-site VPN connections, this is either the Barracuda VPN or Network Access Client, a native VPN client integrated in the operating system, or CudaLaunch.
Web-based resources or apps that do not require SSL tunnels can be accessed via the browser through the SSL VPN service on the firewall. This entry-level access is good for infrequently used internal resources.
For more information, see SSL VPN User Interfaces.
CudaLaunch is a fully managed client for all SSL VPN features. VPN connections are fully integrated. On iOS, CudaLaunch manages the native IPsec client, including updating the configuration in case the VPN settings are changed on the firewall. On Android, CudaLaunch includes a full TINA VPN client; configuration changes are also pushed directly to the client, without interaction from the admin. For Windows and macOS devices, the VPN connection for the Barracuda VPN Client can be downloaded directly from CudaLaunch, but configuration changes of the VPN configuration are not synced.
Barracuda VPN Clients
For client-to-site VPN connections, the VPN Client is chosen to match the VPN protocol configured in the VPN service. For VPN connections using the TINA protocol, you must use the Barracuda VPN or Network Access Client.
For more information, see Barracuda Network Access and VPN Client.
Native IPsec Clients
For IPsec VPN using the IKEv1 or IKEv2 protocol, every standard compliant VPN client should work. Depending on the platform, you may need to adjust the client-to-site configuration to match the requirements of the client. Currently, the native VPN clients on iOS and Android are supported only for IKEv1.