Version 8.0

Version 8.00.05

Issues fixed

• CVE-2016-2108 fix

• Configuration import - profile import fixed

• Upgrade process from v7.05 - Active devices upgrade fixed

Version 8.00.04

Issues fixed

• FCC System - Syslog server - Last user identity syslogs dowload fixed

• FMC collector fix - Flow source graphs are not deleted during FMC restart for listening ports with underscore character in name

• FMC Report - report generation for chapter based on 'All' parent channels of shadow profile is fixed

• Security fixes

Version 8.00.03

Issues fixed

• FMC - Dummy source bugfix

Version 8.00.02

• Netcope card NFB-100G2 support

• Barracuda NG firewall IPFIX stream support

• sflow sent via PPPoE is supported

Issues fixed

• FMC AS list file name can contain special characters

• FMC Reports - computation and display of chapters with bidirectional statistics fixed

• FMC Alert - email address - length of top level domain is not limited to 3 characters any more

• FMC Analysis - persistency of channels selected in "Change displayed channels" form fixed

Version 8.00.01

• Python updated to version 2.6.8

• ntpd updated - Time sychronization works correctly with pfSense now

Issues fixed

• Extended timeout for XML configuration import - avoids failure of import if it contains a large number of channels and profiles.

• Record of the last received userID logs is stored in RAM now to avoid high disk usage in case of high log rate.

• SMB delete operation detected if sent as a part of SET_INFO operation

• Domain name translation now works with records in /etc/hosts file

• Postgres update fixing exploit CVE-2016-0773

• FMC - Analysis - Copying of non-ASCII characters into filter fixed

• FMC - Analysis/Reports - For L3/L4 extended values it displays "N/A" instead of "0"

• FCC - Version - Module buttons fixed

Version 8.00.00

• FMC - Profile live is replaced with a profile AllSources. As a result, flow data from each flow source are natively stored into separate channels with no need for extra filtering. When editing a root profile (= direct child of profile AllSources) only flow sources (= channels of profile AllSources) can be selected. Selection of listening ports is not possible any more.

• FMC - Profile AllSources has been moved from Sources group to the root level.

• FMC - In profile editation form, it is now possible to select item "All" instead of parent channel selection. This option will automatically include any other parent channel added in the future.

• FMC - Content of profile selection menu can be filtered.

• FMC - Alerts can be ordered by selected column.

• FMC - Edit profiles - Profile groups can be expanded and collapsed.

• FMC - Edit profiles - Channel order can be defined in a profile.

• FMC - BGP next/previous AS statistic has been added.

• FMD - Reports page added. Reports can be exported into PDF and sent automatically.

• FMD - Overview - Multiple tabs per user can be created.

• FCC - FMC Config - Listening ports - New column Sampling rate has been added.

• FCC - System - SSL certificate management - Subject Alternative Names can be added into the generated certificate.

• FCC - Quotas Manager - Information about size of FMC graph data has been added.

• FCC - Version - Available Packages - Release notes are now downloaded together with an update package. Also, they are attached to the notification email.

• DHCP and Samba procol monitoring support.

When the migration is finished, each flow source is connected with its channel in the AllSources profile. Data exported by this flow source are stored in its channel.

Each flow source is also connected with listening port which is used by this flow source for exporting flows.

If the current flow source starts to export flows to a different listening port, a new channel will be created for it. Both, the old and the new channel, will be keeping data of the same flow source, but the old one will be keeping data sent to the old listening port and the new one to the new listening port. Both channels' names will be extended with suffixes identifying their listening port.

If a flow source already detected by FMC has not exported a single flow at least 10 minutes before upgrade, it might be mapped to the incorrect listening port during upgrade process. This may lead to creating another channel for this flow source in the moment it exports a first valid flow into collector.

• Every channel of a root profile will be configured in the following manner after upgrade:

  • If all available flow sources were assigned to it before upgrade, it will be configured with the option "All" (see the above list of new features) in his parent channels configuration. Otherwise, it will be assigned with parent channels corresponding to the assigned flow sources.

• Configuration of following plugins will also be migrated during the upgrade:

  • Flowmon ADS

  • Flowmon Data Retention