| Bugfix-163 |
6.3-4 |
Display error on mitigation reports when attackers send more than 4.3 Gbps |
|
| Bugfix-161 |
6.3-4 |
Sensor Top values and percentages can be wrong when the values are very high |
|
| Bugfix-16 |
6.0-29 |
Flow Sensor crash when its RAM consumption reaches 2GB |
|
| Bugfix-157 |
6.3-1 |
Fix harmless error when executing install_console on CentOS 7 |
|
| Bugfix-156 |
6.3-1 |
Sensor Cluster not reporting Latest Value correctly in some circumstances |
|
| Bugfix-155 |
6.3-0 |
Inaccurate Sensor bits/s tops for bandwidths over 4.3 Gbps |
|
| Bugfix-15 |
6.0-27 |
Fix WANsupervisor crash immediately after starting up, in rare conditions |
|
| Bugfix-149 |
6.2-56 |
In the latest patches the data retention for flow collectors was 60 times lower than the configured value |
|
| Bugfix-144 |
6.2-55 |
Fix PDF Anomaly Reports sent through Responses |
|
| Bugfix-141 |
6.2-54 |
Scheduled reports may not be sent after upgrading to 6.2-51 |
|
| Bugfix-140 |
6.2-54 |
Anomaly details show the label Total Packets/s instead of Sum Pkts and Total Bits/s instead of Sum Bits |
|
| Bugfix-139 |
6.2-54 |
The Severity parameter from the Mitigation Options inconsistent with the documentation |
|
| Bugfix-138 |
6.2-54 |
Flow Filter may ignore flows with long durations |
|
| Bugfix-136 |
6.2-53 |
Missing AS graphs on version 6.2-52 |
|
| Bugfix-135 |
6.2-53 |
False "child process ended unexpectedly" error from Flow Filter |
|
| Bugfix-134 |
6.2-53 |
Flow Filter sends debug information to syslog |
|
| Bugfix-130 |
6.2-52 |
Anomaly Widget widget not showing all anomalies on IP/Subnet/Group reports |
|
| Bugfix-13 |
6.0-24 |
Packet Tracer corrupting trace files on rare ocasions |
|
| Bugfix-128 |
6.2-52 |
Hardware Firewall not working when the Filter has the Execution parameter set to Automatically |
|
| Bugfix-126 |
6.2-51 |
Empty printed reports when using Google Chrome and Firefox |
|
