Table of Contents
Advertisement
Bugfixes Included with Barracuda NG Firewall 5.0.3
Barracuda NG Admin
Table 1–6
Barracuda NG Admin
Within the
Network Interface
Type
in a VLAN interface. This issue was fixed.
In rare cases, the
Send Changes
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.
Barracuda NG Installer
Table 1–7
Barracuda NG Installer
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.
Barracuda NG Firewall
Table 1–8
Barracuda NG Firewall
Module
Authentication
Authentication
Authentication
Barracuda OS
Barracuda OS
Barracuda OS
Firewall
10 Release and Migration Notes - Bugfixes Included with Barracuda NG Firewall 5.0.3
Configuration, pop-ups erroneously appeared every time after changing the
button was erroneously disabled within the
Occasionally, a few log lines were missing in the authentication log. This issue was fixed.
Occasionally, the firewall authentication daemon was erroneously blocking requests if these requests
were sent delayed by the respective clients. This issue was fixed.
Active Directory offline group synchronization was erroneously not using SSL even when it was
configured to use it. This issue was fixed.
HDD performance I/O statistics were erroneously not logged. This issue was fixed
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.
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.
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.
Description
Personal Firewall Rules
Description
Description
Appliance Sub Model
Configuration. This issue
Advertisement
Table of Contents
