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

Example - Client-to-Site IKEv1 IPsec VPN with PSK

  • Last updated on

To let users access a client-to-site IPsec VPN without having to install X.509 certificates on their client devices, you can create an IPsec client-to-site VPN group policy using a pre-shared key (PSK). For users with mobile devices that are not managed by a mobile device management platform (MDM), using a PSK is more convenient than having to install client certificates for authentication. To allow multiple concurrent client-to-site connections for a single user, an Advanced Remote Access subscription is required. You can connect from any IPv4 or IPv6 address, as long as an external IPv4 and IPv6 address are configured as a service IP address for the VPN service. Traffic passing through the client-to-site VPN is limited to IPv4.

Client2SiteIPsecXAUTHPSKVPN-01.png

Supported VPN Clients

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

Before You Begin

Step 1. Configure the VPN Service Listeners

Configure the IPv4 and IPv6 listener addresses for the VPN service.

  1. Go to CONFIGURATION > Configuration Tree> Box > Virtual Server > your virtual server > Assigned Services > VPN > Service Properties.
  2. Click Lock.
  3. From the Service Availability list, select the source for the IPv4 listeners:
    • First+Second-IP – The VPN service listens on the first and second virtual server IPv4 address.
    • First-IP – The VPN service listens on the first virtual server IPv4 address.
    • Second-IP – The VPN service listens on the second virtual server IPv4 address.
    • Explicit – For each IP address, click + and enter the IPv4 Addresses in the Explicit Service IPs list.
  4. Click + to add an entry to the Explicit IPv6 Service IPs.
  5. Select an IPv6 listener from the list of configured explicit IPv6 virtual server IP addresses.
    vpn_service_listeners.png
  6. Click Send Changes and Activate.

Step 2. Configure the Client Network, Gateway, and PSK Key

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN > VPN Settings.
  2. Click Lock.
  3. Verify that the default server certificate and key are valid.
    1. Right-click the Settings table and select Edit Server Settings.
    2. Verify that the Default Server Certificate and Default Key are both valid (green). If the Default Server Certificate and Default Key are not valid, see How to Set Up VPN Certificates .
      PSK01.png
  4. In the Server Settings window, click the Advanced tab.
  5. In the IKE Parameter section, enter the IKE PSK key. E.g., pre$haredKey
    PSK02.png

  6. Configure the client network.
    1. Click the Client Networks tab.
    2. Right-click the table and select New Client Network. The Client Network window opens.
    3. In the Client Network window, configure the following settings:

      • Name – Enter a descriptive name for the network.

      • Network Address – Enter the base network address for the VPN clients. E.g., 192.168.6.0

      • Netmask – Enter the netmask. E.g., 24

      • Gateway – Enter the gateway network address. E.g., 192.168.6.254

      • Type – Select routed (Static Route). VPN clients are assigned an address via DHCP (fixed or dynamic) in a separate network reserved for the VPN. A static route on the firewall leads to the local network.

        PSK03-72.png

    4. Click OK.

  7. Click Send Changes and Activate.

Step 3. Configure VPN Group Match Settings

Configure the global authentication settings for VPN tunnels using an external X.509 certificate and group configurations.

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN-Service > Client to Site .
  2. Click Lock.
  3. Click the External CA tab.
  4. Click the Click here for options link. The Group VPN Settings window opens.
    PSK04-72.png
  5. Select the Authentication Scheme:
    • Default Authentication Scheme – The default authentication scheme is used for all VPN group policies.
    • Extract from username – The authentication scheme is appended to the username. The authentication scheme with the appended name is used with the default authentication scheme acting as a fallback if the authentication scheme name is not present on the firewall. E.g., user1@msad1 or user2@domain.com@HQldap.
  6. Select the Default Authentication Scheme from the drop-down list. This authentication scheme must be configured on box level of the firewall.
    PSK05v2.png
  7. Click OK.
  8. Click Send Changes and Activate.

Step 4. Create a VPN Group Policy

The VPN Group Policy specifies the network IPsec settings. You can create group patterns to require users to meet certain criteria, as provided by the group membership of the external authentication server (e.g., CN=vpnusers*). You can also define conditions to be met by the certificate (e.g., O(Organization) must be the company name).

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN-Service > Client to Site.
  2. Click Lock.
  3. Click the External CA tab, and then click the Group Policy tab.
  4. Right-click the table and select New Group Policy. The Edit Group Policy window opens.
  5. Enter a name for the Group Policy.

  6. From the Network list, select the VPN client network.

  7. In the Network Routes table, enter the network that must be reachable through the VPN connection. For example, 10.10.200.0/24

    To route all traffic through the client-to-site VPN tunnel, add a 0.0.0.0/0 network route.

    PSK06.png

  8. Configure the group policy.
    1. Right-click the Group Policy Condition table and select New Rule. The Group Policy Condition window opens.
    2. In the Group Pattern field, define the groups that will be assigned the policy. E.g., CN=vpnusers*
    3. In the Peer Condition section, verify that IPsec Client check box is selected.
    4. To use this group policy for SSL-VPN VPN template resources and CudaLaunch, enable Barracuda Client.
    5. Click OK.

      PSK07.png

  9. Configure the encryption and hashing settings:
    1. Click the IPSec tab.
    2. Clear the check box in the top-right corner.
    3. From the IPsec Phase II - Settings list, select the entry that includes (Create New) in its name. For example, if you choose Group Policy as a name, the entry name is Group Policy (Create new)
    4. Set the following encryption algorithm settings for Phase II:
      • Encryption – Select AES256.
      • Hash Meth. – Select SHA for iOS 12 or lower and Android 5.2 or lower. Select SHA256 for Android 6.0 to 7.1.2 and iOS 13 and higher, and SHA512 for Android 7.1.2 or higher.
      • DH-Group – Select Group2.

      • Time – Enter 3600
      • Minimum – Enter 1200
      • Maximum – Enter 28800
      C2S_00.png
    5. Click Edit IPsec Phase I and select the encryption algorithm in the For XAuth Authentication section:
      • Encryption – Select AES256.
      • Hash Meth. – Select SHA. 
      • DH-Group – Select Group2.

      • Time – Enter 3600
      • Minimum – Enter 1200
      • Maximum – Enter 86400
      C2S_01.png
    6. Click OK.
  10. Click OK.
  11. Click Send Changes and Activate.

Step 5. Add Access Rules

Add two access rules to connect your client-to-site VPN to your network.

For more information, see How to Configure an Access Rule for a Client-to-Site VPN.

Monitoring VPN Connections

On the VPN > Client-to-Site page, you can monitor VPN connections.

C2S_status_connected.png

The page lists all available client-to-site VPN tunnels. In the Tunnel column, the color of the square indicates the status of the VPN:

  • Blue – The client is currently connected.
  • Green  The VPN tunnel is available, but not in use. 
  • Grey – The VPN tunnel is disabled. To enable the tunnel, right-click it and select Enable Tunnel.

For more information about the VPN > Client-to-Site page, see VPN Tab.

Troubleshooting

To troubleshoot VPN connections, see the /yourVirtualServer/VPN/VPN and /yourVirtualServer/VPN/ike log files. For more information, see LOGS Tab.

Next Steps

Configure the remote access clients to connect to the client-to-site VPN.

For more information, see Remote Access Clients.

Last updated on