Barracuda Networks NG FIREWALL 5.0.3 Release Notes page 11

Table 1–8
Barracuda NG Firewall
Module
Firewall
HTTP Proxy
Mail Gateway
Network
Network
Network
Network
Network
NG Control Center
NG Control Center
NG Control Center
NG Control Center
SNMP Service
VPN Service
VPN Service
VPN Service
VPN Service
11 Release and Migration Notes - Bugfixes Included with Barracuda NG Firewall 5.0.3
The detection of large packet sizes (PMTU discovery) did not work in conjunction with local redirection
rules. This issue was fixed.
Infrequently, the Proxy GUI in Barracuda NG Admin was not fed anymore with up-to-date status
information due to an issue within the HTTP Proxy module. This issue was fixed.
Due to a database problem, the Mail Gateway erroneously went down on rare occasions and had to be
restarted manually. This issue was fixed.
On VFxxx virtual machines, it was erroneously not possible to select previously configured additional
interfaces directly after the virtual machine was installed. This issue was fixed.
The authentication daemon erroneously crashed when a device tried to authenticate while at the same
time leaving the WiFi's transmission range. This issue was fixed.
The activation of bonding on a unit could under certain circumstances result in the creation of erroneous
MAC mapping tables. This issue was fixed.
An erroneous match for the priority of a 3G or xDSL routing rule caused previously assigned source
addresses to remain part of the source match condition, which was leading to the creation of a stack of
rules that eventually exhausted the maximum number of rules. This issue was fixed.
The IP address for a DHCP link that had been configured to use Dynamic DNS was erroneously not
updated as intended. This issue was fixed.
In conjunction with different firmware release versions on a Barracuda NG Control Center and its
managed units, certain configuration options may erroneously have been unavailable on the NG Control
Center, such as e.g. URL filter categories for a 4.2.x cluster on a 5.x NG CC. This issue was fixed.
It was erroneously not possible to add a WLAN node to the Repository. Any attempt to do so failed with an
error pop-up message saying Copy to Repository Status: Error. This issue was fixed.
In very rare occasions and only in conjunction with different release versions on an NG CC and its
managed units, Barracuda NG Control Center assigned erroneous default NIC driver names to certain
managed units. This issue was fixed.
Under certain circumstances, Repository directories could erroneously get wrong label names after a
migration process. This issue was fixed.
Blocked services were through SNMP erroneously indicated as being started. This issue was fixed.
At very rare occasions, the internet key exchange (IKE) service crashed, resulting in a short service
interruption with currently open VPN tunnels, as these tunnels went down and were then automatically
re-created.
NAT traversal did erroneously not work with site-to-site tunnels. This issue was fixed.
Terminating VPN tunnels via Barracuda NG Admin was on rare occasions leading to a kernel panic. The
same problem could also occur in conjunction with Access Control Service connections on certain ports.
This issue was fixed.
The VPN Service occasionally crashed with certificates that contained long subject names. This issue was
fixed.
Description