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

Release Notes 8.3.1

  • Last updated on

What's New in Version 8.3.1

Private Service Edge

Barracuda CloudGen WAN now provides private service edge for hybrid deployments. Private service edge is ideal for organizations that need to follow certain geopolitical requirements or need full control over the data plane. Private service edge devices provide the same scope of security and networking functionality as the cloud service and are administrated and maintained via a central management platform.

This feature will be available in 2 to 3 weeks.

Secure Connector

The Barracuda Secure Connector is now available for Barracuda CloudGen WAN. The Secure Connector offers large-scale remote access capabilities. It enables the ever-growing number of IoT devices and micro-networks to securely connect to a central or distributed corporate datacenter. In such a scenario, a large number of small Secure Connector appliances connect via TINA VPN to the Barracuda CloudGen WAN Gateway.

Currently available Secure Connector hardware:

The Secure Connector can be claimed and deployed in the same way as other CloudGen WAN hardware.

Note, however, two exceptions:

  1. The operating system of the Secure Connector appliance must be updated before it is connected to the CloudGen WAN service. Please contact Barracuda Networks for the update of the Secure Connector appliance operating system.
  2. The Barracuda Secure Connector is available for both the Barracuda CloudGen Firewall and Barracuda CloudGen WAN. Note, however, that as soon as you associate it with one of them, you will no longer be able to associate it with the other one.

Secure Connector appliances send all traffic to the Barracuda CloudGen WAN gateway, where gateway ACLs and security/SD-WAN policies are applied.

Stand-Alone Sites Are Now Available

Barracuda CloudGen WAN now allows you to configure stand-alone sites. These sites are not connected to a gateway, or a virtual WAN in Microsoft Azure, and can be centrally managed through the Cloud Web UI. Customers only need a Barracuda Cloud Control account and must subscribe to the Barracuda CloudGen WAN service in Microsoft Azure. An existing site can be reconfigured to become a stand-alone site. Stand-alone sites support point to site.

existing_site_gw_none831.png

For more information, see How to Create a Stand-Alone Site Configuration in Barracuda CloudGen WAN .

Workspaces

Workspaces allow you to create configuration units that are completely independent from each other. For example, you can create a Campus workspace and an Engineering workspace where different security and SD-WAN policies are applied. 


workspaces2_831.png

For each individual workspace, you can configure the following:

  • Virtual WAN
  • Gateways
  • Private Cloud Edge
  • Sites
  • Users
  • Custom apps
  • SD-WAN policies
  • Security policies
  • Audit Log

In addition, the following workspace settings are configured for each workspace separately:

  • Firmware Update Windows
  • Forwarded Domains
  • Log Analytics

A workspace can be connected to only one virtual WAN in Microsoft Azure.

You can easily switch between workspaces by clicking on the workspace at the top. From the drop-down menu, you can select the workspace you want.

workspaces1_831.png

For more information, see Workspaces.

IPS

As of firmware 8.3.1, Barracuda Networks has implemented its own IPS engine, which will allow greater flexibility to address customer needs in the future. The signature database is provided by IDappcom. For more information on the signature database, see https://www.idappcom.co.uk/.

All false positive rules will be deleted when updating to 8.3.1 since a new set of patterns will be used.

For more information, see IPS and Migration Notes 8.3.1.

Open SSL Update

Open SSL has been updated to the newest version 3.0.1. 

Routing Intent

Barracuda CloudGen WAN supports Microsoft Azures routing intent. For more information, see https://docs.microsoft.com/en-us/azure/virtual-wan/how-to-routing-policies. This feature will be available in 2 to 3 weeks.

Gateway Drop-Down Menu Added in Site Configuration

Barracuda CloudGen WAN now allows you to change the gateway that a site is connected to directly in the settings of a site.

site_gw_drop_831.png

For more information, see How to Change the Gateway of a Site.

Improvements Included in Version 8.3.1

  • After restarting the VPN service, all BGP routes come up again as expected. BNNGF-79770
  • An issue where some interfaces were not displayed has been resolved. BNNGF-79182

  • A more precise text appears when hovering your mouse over a connection state. SWCS-1520 

  • A new connection state called "Sync" has been added. This status indicates that the connection of a high availability cluster has been synced from the primary appliance to the secondary one. SWCS-1564

  • The information column of the Recent and Live connections is now displayed by default. SWCS-1619

  • Password changes of sites work as expected. SWCS-1628

  • Azure Load Balancer probes are now handled properly. BNNGF-82114

  • Unlicensed appliances now display a warning. BNNGF-77880

  • The WAN hub now displays all errors correctly. BNNGF-76233

  • An issue where unlicensed appliances were not provisioned has been resolved. BNNGF-76232

  • Client-to-site traffic now works as expected. BNNGF-76321

  • Removing old log files now works as expected. BNNGF-77020

  • DHCP client leases no longer produce high memory usage. BNNGF-78135

  • An issue where the firmware update took longer than 15 minutes has been resolved. BNNGF-78376

  • Fixed excessive probing by site appliances for certain providers that over-provision the line.

Known Issues

  • After changing the provider pinning of a WAN interface of a site, the VPN service must be restarted. BNNGF-67946
  • Incoming SD-WAN connections of a private gateway always use the first WAN connection. BNNGF-84765

Migration Notes

For more information on the migration to firmware 8.3.1, see Migration Notes 8.3.1.

Last updated on