| Bugfix-645 |
8.5-6 |
Fix a bug that caused Flow Sensor to use too much RAM when monitoring hundreds of interfaces |
|
| Bugfix-539 |
8.2-13 |
Fix a bug that affected the Dynamic Parameter {filtering_rule_log_*} |
|
| Bugfix-501 |
8.1-18 |
Fix a bug preventing Sensor Logs to be shown in Anomaly Reports when using a Sensor Cluster |
|
| Bugfix-664 |
9.0-5 |
Fix a bug introduced in 9.0-1 that causes Sensor Cluster to report huge traffic after adding a custom decoder |
|
| Bugfix-614 |
8.3-20 |
Fix a bug introduced in 8.3-18 that affected the per-subnet thresholds |
|
| Bugfix-220 |
7.0-3 |
Fix a bug in the World Clock window introduced in 7.0-1 |
|
| Bugfix-233 |
7.0-8 |
Fix a bug in Graphs & Storage Configuration with less than 3 RRAs |
|
| Bugfix-268 |
7.1-7 |
Fix a bug affecting the correct detection of profile anomalies |
|
| Bugfix-585 |
8.3-11 |
Fix a bogus message generated by SNMP Sensor |
|
| Bugfix-506 |
8.2-3 |
Fix a 'Duplicate entry' error that appeared while upgrading to 8.2 |
|
| Bugfix-670 |
9.0-6 |
Fix a "Destination tracking capacity exceeded" warning in Flow Sensor |
|
| Bugfix-271 |
7.1-8 |
Filters configured with the DPDK engine did not apply filtering rules for spoofed attacks |
|
| Bugfix-30 |
6.0-42 |
Filtering rules generated by Filter Clusters not correct in some cases for TTL values |
|
| Bugfix-73 |
6.2-28 |
Filter not showing Software Firewall statistics when Netfilter Table is set to Raw |
|
| Improvement-19 |
6.0-31 |
Filter generates iptables rules in the raw table, not filter table, for an improved packet filtering performance |
|
| Improvement-100 |
6.2-42 |
Faster concurrent access to various Console reports |
|
| Bugfix-135 |
6.2-53 |
False "child process ended unexpectedly" error from Flow Filter |
|
| Bugfix-50 |
6.1-9 |
Fake anomaly when the Graphs & Storage configuration changes while a Sensor Cluster is active |
|
| Improvement-602 |
8.3-15 |
Extend the Withdrawal Restrictions of BGP Connectors to the announcements sent by Filter |
|
| Feature-523 |
8.2-9 |
Extend the Redirect (IP/VRF) field in ExaBGP Connector to allow entries for IPv4 and an IPv6 address |
|