Actions
Bug #4824
closedFilterting firewall logs by port returns excess results
Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Web Interface
Target version:
-
Start date:
07/10/2015
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.2
Affected Architecture:
Description
Hi,
If you filter firewall logs by e.g. port 25, the search results appear to be 25 so results include e.g. 1251 not just 25.
Tim
Updated by Tim Boothby about 10 years ago
The bold 25 above should have read asterisk25asterisk (as in wildcard).
Updated by Jim Pingle about 10 years ago
- Status changed from New to Rejected
That is expected behavior. It matches based on regex/substrings. You can use regex anchors to limit what it matches, however. For port 25 and only 25, match on '^25$' for example.
Actions