This page contain the list of registered traffic classes with the interface for creating, removing, or editing them. A traffic class can be removed only if it is not used at the moment. Otherwise, in the first place it is necessary to remove all entities (services, etc.) that refer to it. Once a traffic class is removed, the traffic belonging to it would pass for unidentified in the control center reports. At the same time, in the web interface reports the removed traffic class would continue to show up as existing.
Below is the list of traffic class parameters and their meanings:
![]() |
Format of the raw traffic data files has been altered in UTM5.3-001, so that the files saved in earlier UTM5 versions can no longer be read. |
Besides that, the traffic classes page contains interface for working with subclasses. The interface consists of the following buttons.
Traffic subclass is characterized by the following parameters:
If Skip is checked, the affiliation with subclass is interpreted negatively in the classification, i.e. it means that the traffic does not belong to the given class and needs to be checked against other classes. This may be useful if some address or a group of addresses needs to be pick out as a separate class.