It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Network Access Client

This Firmware Version Is End-Of-Support

Documentation for this product is no longer updated. Please see End-of-Support for CloudGen Firewall Firmware for further information on our EoS policy.

How to Create a *.vpn File

  • Last updated on

You can import VPN profiles and Barracuda Personal Licenses to the Barracuda Network Access Client and the Barracuda VPN Client using configuration files with the suffix *.vpn  that can be configured and created within Barracuda Firewall Admin (for the importing process, see How to Import a *.vpn File into the VPN Client). Follow the instructions on this page to learn how to export a VPN profile from Barracuda Firewall Admin.

Creating a *.vpn File from a Barracuda Personal License

Before creating the *.vpn file, you must configure a VPN template and configure a Barracuda Personal License to be exported in the file.
  1. In Barracuda Firewall Admin, navigate to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN-Service > Client to Site.
  2. Click Lock.
  3. In the Pool Licenses tab, attach the VPN profile template to a Barracuda Personal License:
    1. Open a previously prepared Barracuda Personal License by double-clicking it.
    2. Select the configuration template to be used from the Template list, as shown in the figure below. 
    3. If required, edit the template by clicking the Template button.
      change_pers_lic.png
  4. Click Export to File and select Export to *.vpn file to export the VPN profile containing your license.
    export_vpn_file.png
  5. On the Export VPN Profile page, enter a meaningful name for the profile into the Description field and adjust the other parameters as necessary.
    edit_file.png
  6. Click OK.
  7. A dialog appears asking you to set a license password. You can either type in a password and click OK, or skip the password configuration by clicking No Password.
  8. Choose a location to save the file, enter a name for the file, and click Save.

Creating a Group Policy-based *.vpn File

Before creating the *.vpn file, you must configure a VPN template and configure VPN group settings to be exported in the file.
  1. In Barracuda Firewall Admin, navigate to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN-Service > Client to Site.
  2. Click Lock.
  3. Navigate to Group Policy in the External CA tab.
  4. Double-click a group policy in the list. The Edit Group Policy window opens.
    edi_group.png
  5. If necessary, modify the profile settings as needed. 
  6. Click Export to File in the bottom of the window.
  7. On the Export VPN Profile page, enter a name for the profile into the Description field. 
  8. Adjust the other parameters as necessary.
  9. Click OK.
    export_vpn_details.png
  10. A dialog follows asking you to set a password for the license. You can either type in a password and click OK, or skip the password configuration by clicking No Password.
  11. Choose a location to save the file, enter a name for the file, and click Save.

Editing the Contents of a *.vpn File

A *.vpn file is a ZIP archive containing a <profilename>.ini file and, if applicable, a <licensename>.lic file. These files are extracted and processed by the VPN Client during the import. To manually alter the contained profile.ini file (assuming you already have a *.vpn file), complete the following steps:

  1. (Optional) Rename the file from <filename>.vpn to <filename>.zip
  2. Open the *.vpn file using WinZIP, WinRAR, or another compressing / uncompressing tool that can handle ZIP files.
  3. Extract the <profilename>.ini file.
  4. Modify the extracted file as needed.

    For more information on the profilename.ini file's syntax, see Adaptation of Profile Creation Using an *.ini File or contact Barracuda Networks Support.

  5. Update the archive by replacing the file inside with the modified version.
  6. If applicable, rename the file back from <filename.zip> to <filename>.vpn.