We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

How to Configure a Client-to-Site VPN Group Policy

  • Last updated on

Supported VPN Clients

Although any standard-compliant IPsec client should be able to connect via IPsec, Barracuda Networks recommends using the following clients:

Before You Begin

Step 1. Enable the VPN Service on a Network Interface

Enable the VPN service on a static IP address. If you do not have a static WAN IP address, you must enable the VPN service for a static internal interface and then redirect incoming connections to the VPN service with an access rule.

Static (fixed) WAN IP Address

To enable the VPN service for the static network interface:

  1. Go to NETWORK > IP Configuration.
  2. In the Static Interface Configuration section, click Edit to configure your static WAN interface. 
  3. In the Edit Static Network Interface window, select the VPN Server check box.

    If SSL VPN service is also enabled for this interface, go to VPN > Settings and disable Listen on Port 443 for the VPN service.

  4. Click Save
Dynamic (DHCP/3G/PPPoE) WAN IP Address

You must have an active DynDNS account for the client to connect to the dynamic IP address. For more information on creating a DynDNS account, see http://www.dyndns.org.

To use the VPN service with a dynamic WAN IP address, run the VPN service on an internal IP address. Do not use the management IP address; instead, add a secondary IP address. Then, create an access rule to redirect all incoming VPN traffic from the dynamic interface to the VPN service.

  1. Go to NETWORK > IP Configuration.
  2. Enable dynamic DNS:
    1. In the Dynamic Interface Configuration section, click Edit to configure the dynamic WAN interface. 
    2. In the Edit Dynamic Network Interface window, enable Use Dynamic DNS.
    3. Enter the DynDNS Hostname and authentication information.

    4. Click Save.
  3. In the Management IP Configuration section, enter a secondary IP address: 
    • IP Address – Enter an IP address that is free in the local network. For example, if the MIP address is in the network.
    • VPN Server – Select this check box. 


  4. Click Add.

Create an access rule to redirect incoming VPN connections on the dynamic interface to the VPN server listening on the local IP address. For more information, see How to Configure an Access Rule for a Client-to-Site VPN.

Step 2. (Certificate Authentication Only) Upload or Create Certificates

When using certificate authentication, use a third-party PKI to create the VPN and client certificates. For more information on how to create certificates, see How to Create Certificates with XCA and How to Create Certificates for a Client-to-Site VPN.

The SubAlt name of the VPN server certificate must be DNS: examplevpn.domain.com or DNS: *. If you are using an FQDN, it must resolve to the IP address of the firewall VPN service.

  1. Go to ADVANCED > Certificate Manager.
  2. Click Upload. The Upload Certificate window opens.
  3. Enter the following details:
    • Certificate Name – Enter VPN Certificate
    • Certificate Type – Select the type of certificate you want to upload.
    • Add to VPN Certificates – Enable the check box.
    • Certificate File – Select the certificate file you want to upload.
  4. Click Save.

Step 3. Configure Client-to-Site VPN Settings

Configure user authentication and IPsec settings.

Step 3.1 Configure User Authentication and Select the Certificate
  1. Go to VPN > Client-To-Site VPN
  2. In the Settings section, select a User Authentication method. You can use local or external user authentication. For more information, see Authentication.
  3. (Certificate Authentication Only) From the Local Certificate list, select the certificate that you created in Step 2. E.g., VPNCertificate.
  4. Click Save.
Step 3.2 Configure IPsec Settings for Authentication

Configure the authentication type and, if needed, the encryption algorithms for IPsec phase 1 and 2.

  1. Go to VPN > Client-To-Site VPN.
  2. In the IPsec Settings section, select the Authentication type.
  3. (optional) Configure the IPsec Phase 1 Settings and IPsec Phase 2 Settings.

    If you want to use iOS or Android devices as VPN clients, do not change the default IPsec Phase 1 and Phase 2 settings.


  4. Click Save.
Step 3.3 Create a VPN Group Policy

Define the VPN clients and network information to be passed to client.

Access policies are matched based on the Allowed Group of the access policy from top to bottom. Make sure access policies are entered so the more specific allowed groups are on the top of the list and the generic * conditions are on the bottom of the list.

  1. Go to VPN > Client-To-SiteVPN.
  2. In the VPN Access Policies section, click Add Access Policy
  3. In the Add VPN Access Policy window, configure the following settings: 
    • Name – A name for the access policy.

      The name of the access policy is referred to as group name on iOS and Android devices.

    • Client Network – The network that the client will be assigned to. E.g.,

    • (Optional) Domain – The domain assigned to the client.
    • First DNS – The IP address of the DNS server.
    • Published Networks – The local networks available for the VPN client.

      Add to the Published Networks to allow the client to access the Internet through the VPN tunnel.

    • IPsec Phase 2 – The IPsec Phase 2 settings that you configured in the IPsec Settings section.
    • No Split Tunnel Mode – Enable in order to lock down the client to connect only to the Published Networks of the VPN tunnel. (Applies to Windows hosts using the Barracuda VPN Client.)

      Enabling this option blocks VPN access for all non-Windows clients!

    • Allowed Peers – Enable IPsec Client for mobile devices and third-party IPsec clients and Barracuda VPN Client to be able to connect with the Barracuda VPN Client.
    • Allowed Groups – The groups that are allowed to connect. To allow all groups, enter an asterisk (*).
    • Use for CudaLaunch – Enable self-provisioning on Windows, macOS, or iOS devices for remote clients using the CudaLaunch portal. For more information, see CudaLaunch.
      Configure the following settings:
      • CudaLaunch Server – Enter the IP address of the server providing CudaLaunch.
      • Allowed Groups – Enter the user groups that the policy applies to. Click after each entry. You can use question marks (?) and asterisks (*) as wildcard characters.
  4. Click Save.

Step 4. Configure Clients

Configure VPN clients to connect to the IPsec VPN with certificate authentication.

Barracuda VPN Clients

Configure the Barracuda VPN Client to connect to the IPsec VPN with the certificate authentication you just created. You can download the Barracuda VPN Client from the Barracuda Download Portal. To install the client, you must have administrative rights. Reboot the computer after the installation.

Configure a profile for connecting to the IPsec VPN:

  1. Start the Barracuda VPN Client.
  2. In the left pane, click Preferences.
  3. In the Barracuda VPN Control window, right-click the default profile and select Modify Profile. 
  4. In the Properties window, specify these settings:
    • Certificate – Select X509 authentication.
    • Remote Server – Enter the WAN IP address or DynDNS name (e.g., or bfw-vpn.dyndns.org) in the Host names or IP addresses of remote server field.
  5. Click OK
  6. Close the Barracuda VPN Control window.

After configuring the Barracuda VPN Client, you can connect to the IPsec VPN:

  1. Start the Barracuda VPN Connector.
  2. Enter your Username and Password.
  3. Click Connect. 

You are now connected to the client-to-site IPsec VPN with the Barracuda VPN Client.


The connection status is displayed on the VPN > Active Connections page.

Mobile Clients

For instructions on configuring mobile clients, see these articles:

Mobile OS Supported Version Article
Apple iOS 5.2 or above How to Configure the Apple iOS VPN Client for IPsec Shared Key VPN
Android 4.0 or above How to Configure the Android VPN Client for IPsec Shared Key VPN
Third-party IPsec VPN Clients

The firewall adheres to the IPsec standard. Any third-party IPsec client implementing this standard can connect to the IPsec VPN.

Last updated on