
6 Release and Migration Notes - General
General
GPL Compliance Statement
This product is in part Linux based and contains both Barracuda Networks proprietary software components and open source components in modified and unmodified
form. A certain number of the included open source components underlie the GPL or LGPL or other similar license conditions that require the respective modified or
unmodified source code to be made freely available to the general public, this source code is available on http://source.barracuda.com.
Please also refer to the chapter
Warranty and Software License Agreement of the Barracuda NG Firewall 5.2.3 Administrator’s Guide documentation located in the
documentation section on www.barracuda.com and on each accompanying USB thumb drive.
Read this document before updating your system
If you are going to update from release version 4.2 to Barracuda NG Firewall 5.2.3 via firmware version 5.0 (no direct
update is possible!), Barracuda Networks strongly recommends to study the Barracuda NG Firewall 5.0 Migration
Instructions and also the Barracuda NG Firewall 5.2 Migration Instructions available for download at
https://login.barracudanetworks.com, as, under certain circumstances, no countermanding is possible once the
updating process was initiated.
There you will also find in-depth information on new features and changes in terminology that have been introduced
with release version 5.0.
Starting with Barracuda NG Firewall 4.2.13, OVA images for VMWare were made available. OVA images based on
minor release 4.2.13 have a bug which might lead to loss of the current network configuration when updating to
Barracuda NG Firewall minor release version 5.2.3 via major release version 5.0.
Please make sure to configure your network settings before updating virtual appliances based on 4.2.13 OVA
images using Barracuda NG Admin at least once. Also, a network activation is required.
This issue does not apply to fresh installations based on 5.2.3 OVA images.
Prior to firmware release version 5.2.3 it was for compatibility reasons possible to establish a client-to-site VPN
connection by only using any VPN client even though Exclusive Network Access (ENA) was configured on the
Barracuda NG Firewall.
With 5.2.3, it is now implicitly necessary to have the NG Personal Firewall including the packet filter SPAC installed
on the client, otherwise a connection to the VPN server will be prevented.
One time password authentication with Verisign’s Unified Authentication Tokens will only work if the new OTP
preserves State configuration parameter in the RADIUS configuration of Barracuda NG Firewall is properly set.
This parameter is only visible in Advanced mode.
The Barracuda NG Firewall may reboot after installation. If not, Barracuda Networks recommends performing a
manual reboot.
Comentários a estes Manuais