Last Modified: Oct 06, 2020
See more info
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4
12.0.0, 11.6.0 HF5
Opened: Oct 14, 2014
When traffic didn't map to any of the supported Application Layer protocol/service it was classified as Unknown which is misleading and doesn't provide enough granularity.
Misleading classification results
Traffic didn't map to any of the supported Application Layer protocol.
Instead of classifying traffic as Unknown we will now tag flows as TCP or UDP depending what type of traffic is seen by the classification library