Actions
Bug #9140
open
Unexpected rule can be displayed when looking up filter log entry with multiple matching rules
Status:
New
Priority:
Very Low
Assignee:
-
Category:
Logging
Target version:
-
Start date:
11/20/2018
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.x
Affected Architecture:
Description
When using Port aliases, in the firewall log, when clicking on 'action' the triggering port seems to always be the first of the list.
As for the images, the triggering port is the 21, the port shown in 'detail' is 1001
the port list goes something like: 1001, 21, ...
Files
Updated by 
Actions