Installation guide

11 Release and Migration Notes - Bugfixes Included with Barracuda NG Firewall 5.0.5
Bugfixes Included with Barracuda NG Firewall 5.0.5
Barracuda NG Installer
Barracuda NG Firewall
Table 1–7 Barracuda NG Installer
Description
In rare cases, units were erroneously detected as XEN units. This issue was fixed.
Table 1–8 Barracuda NG Firewall
Module Description
Access Control Service
An issue with the Dutch keyboard layout causing the VPN applet to erroneously activate the German
keyboard layout was fixed.
Barracuda OS
Deactivated box services were erroneously displayed with red status indicators in Control > Processes.
This issue was fixed.
Barracuda OS
On legacy netfence edge units, the status LED erroneously kept flashing after an installation process was
already finished. This issue was fixed.
Barracuda OS
Firewall rule names exceeding a length of 64 characters were breaking their respective log files, which
was on Flash-based units occasionally resulting in the log service consuming all available system
resources, eventually ending up in a system crash. This issue was fixed.
Barracuda OS
BIND was updated in order to fix a vulnerability.
See also https://www.isc.org/software/bind/advisories/cve-2011-4313.
Firewall
On very rare occasions, a unit could freeze due to the usage of local redirect rules. This issue was fixed.
Firewall
In rare cases, adding or deleting tickets in the ticketing system’s landing page failed in saving changes to
the database, throwing users back to the login page instead. Furthermore, trying to print a ticket using
Internet Explorer 9 brought up the following error message:
Your browser is not supported. Please use a supported browser!
Such an attempt to print a ticket in Firefox would print the ticket as intended but would also subsequently
redirect the user to an empty page.
These issues were fixed.
Firewall
Setting SynFloodProtection to Inbound and having a Redirect firewall rule cycling through two
destination servers could cause a problem with destination server reachability in case one of the
destination servers went down and came back to life later. It was not recognized as being reachable then.
This issue waa fixed.
Firewall
The landing page did not allow usage of the ’ß’ character in user names. This issue was fixed.
Firewall
An issue regarding invalid TCP header checksum errors in local connections, mostly VPN TCP
connections, with TCP Checksum Validation switched off in the general firewall configuration, was fixed.
Firewall
On Internet Explorer 9, the landing page did at a certain point not redirect users after the welcome screen
as intended. Instead, it reloaded itself but with a missing background image. This issue was fixed.
Firewall
The NG Firewall Ticketing System (ticketing management feature at the landing page) erroneously
displayed a validity date that was one month back. This issue was fixed.
HTTP Proxy
Setting the Safe Search option to Strict had no effect. This issue was fixed.