Barracuda Networks SP4 Instrukcja Użytkownika Pobierz pdf (Strona 46)

46 Release and Migration Notes - Bugfixes Included with Barracuda NG Firewall 5.2.3

Barracuda OS

The activation of standard hardware (SF) licenses did under certain circumstances fail, generating

obfuscating and meaningless error messages. The problem appeared only on hardware units, not on

virtual machines. This issue was fixed.

Control Center

Downloaded files were erroneously not restored on reinstalling the system. This issue was fixed.

Control Center

Activating SF single licenses erroneously failed on Barracuda NG Control Center units. This issue was

fixed.

Firewall

On very rare occasions, a unit could freeze due to the usage of local redirect rules. 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.

Firewall

In rare cases, units with 64-bit multi-core architecture could freeze due to a problem related to inbound

IPv6 traffic. 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

In firmware release version 5.2.2, MSCHAP authentication did in certain cases not work if the firewall’s

Intrusion Prevention System (IPS) feature was activated. This issue was fixed.

Firewall

Filling in an IP address and an interface name within IP / Ref in a Network Object while the Kernel Ruleset

is set to yes prevented the respective firewall rule from working. This issue was 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 was fixed.

Firewall

The landing page did not allow usage of the ’ß’ character in user names. This issue was fixed.

Firewall

Synchronous pinging from one Windows system to another Windows system and vice versa through the

Firewall was erroneously not possible. 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.

HTTP Proxy

Setting the Safe Search option to Strict had no effect. This issue was fixed.

HTTP Proxy

The HTTP Proxy was under certain circumstances not able to start when no authentication text was

configured. This issue was fixed.

Mail Gateway

In rare cases, HA synchronization of the Mail Gateway did not work as intended as email data was synced

to the primary unit but at the same time not deleted from the secondary box. This would then cause a loss

in performance and raise the latency of the email flow after a while, or it could even result in exceeding the

maximum session limit. This issue was fixed.

Network

Configuring an IPv6 route with unnecessary, but valid leading zeros led to the route displayed as wild

although the notation was valid and the route was working as intended. This issue was fixed.

Network

On models with WiFi, it was erroneously not possible to choose the ath2 WiFi interface within the routing

configuration. This issue was fixed.

Network

In rare cases, OSPF introduced routes were not introduced as intended, because, under certain

circumstances, summary routes received from OSPF neighbors were not written into the routing table.

This issue was fixed.

Table 1–7 Barracuda NG Firewall

Module Description

1 2 ... 41 42 43 44 45 46 47 48 49 50 51 ... 61 62

Komentarze do niniejszej Instrukcji

Brak uwag

Barracuda Networks SP4 Instrukcja Użytkownika Strona 46

Komentarze do niniejszej Instrukcji