Barracuda Networks NG FIREWALL, Release Notes

Page: 10 / 24

10 Release and Migration Notes - Bugfixes Included with Barracuda NG Firewall 5.0.3
Bugfixes Included with Barracuda NG Firewall 5.0.3
Barracuda NG Admin
Barracuda NG Installer
Barracuda NG Firewall
Table 1–6
Barracuda NG Admin
Description
Within the Network Interface Configuration , pop-ups erroneously appeared every time after changing the Appliance Sub Model
Type in a VLAN interface. This issue was fixed.
In rare cases, the Send Changes button was erroneously disabled within the Personal Firewall Rules Configuration . This issue
was fixed.
Updating two units within two different tabs in Barracuda NG Admin at the same time resulted in failing update procedures. This
issue was fixed.
Table 1–7
Barracuda NG Installer
Description
Barracuda NG Installer was for virtual appliances in some cases erroneously not setting the model version as intended, leading to
configuration problems in Barracuda NG Admin subsequent to the installation process. This issue was fixed.
Barracuda NG Installer failed to execute automated USB thumb drive installations on flash-based appliances if there were additional
USB devices connected to the appliance. The following error message was generated:
An error occurred finding the installation image on your hard drive. Please check your images and
try again.
This issue was fixed.
Table 1–8
Barracuda NG Firewall
Module Description
Authentication Occasionally, a few log lines were missing in the authentication log. This issue was fixed.
Authentication Occasionally, the firewall authentication daemon was erroneously blocking requests if these requests
were sent delayed by the respective clients. This issue was fixed.
Authentication Active Directory offline group synchronization was erroneously not using SSL even when it was
configured to use it. This issue was fixed.
Barracuda OS HDD performance I/O statistics were erroneously not logged. This issue was fixed
Barracuda OS An issue within the VPN Client-to-Site and SSL VPN NAC licenses prevented these licenses from being
correctly recognized on VF1000 (and probably also other Vxxxx) virtual appliances. This issue was fixed.
Barracuda OS On VF250 virtual machines, it could erroneously happen that P2P detection generated an error stating
that the license for P2P detection was limited to 100 units, although the license was not limited to this
value. This issue was fixed.
Firewall Big amounts of global firewall objects were, even if they were not referenced in a ruleset, leading to high
memory consumption. This issue was fixed.