Bug #13806
closedSuricata interface rules cannot be viewed.
Added by Marcos M over 2 years ago. Updated over 2 years ago.
100%
Description
Tested on the latest version on the dev branch.
No matter which rule is selected in the drop-down, the custom rules always gets loaded - see attached.
Files
suricata.png (43.4 KB) suricata.png | Marcos M, 12/26/2022 10:00 PM | ||
Suricata_selected_rules.png (79.1 KB) Suricata_selected_rules.png | Selected rules category screenshot | Bill Meeks, 12/27/2022 02:03 PM | |
suricata_categories.png (356 KB) suricata_categories.png | Marcos M, 12/27/2022 02:41 PM | ||
SID_MGMT_Emerging_DNS_enabled.png (39.9 KB) SID_MGMT_Emerging_DNS_enabled.png | Emerging-DNS rules auto-enabled via SID MGMT | Bill Meeks, 12/27/2022 04:22 PM | |
Emerging_DNS_category.png (101 KB) Emerging_DNS_category.png | Emerging-DNS category selected | Bill Meeks, 12/27/2022 04:22 PM |
Updated by Bill Meeks over 2 years ago
Can you post additional details? I cannot reproduce this issue on my test virtual machine. Do you show any rule categories selected on the CATEGORIES tab? The Suricata built-in rules are always selected by default and should be showing, although those can be disabled by the user and then would not show.
Was this from an existing Suricata install that was upgraded, or is this a green-field install on a freshly imaged machine?
Attached is a screenshot from my test machine showing the Emerging-Scan rules selected and displayed on the RULES tab. I can also select and display any other rule category from the drop-down selector.
Updated by Marcos M over 2 years ago
- File suricata_categories.png suricata_categories.png added
It's a fresh install and configuration. All categories do show correctly (see attached) - they are currently being managed by the enable/disable SID files.
Updated by Bill Meeks over 2 years ago
Marcos M wrote in #note-2:
It's a fresh install and configuration. All categories do show correctly (see attached) - they are currently being managed by the enable/disable SID files.
Hmm...that may be the key (using SID MGMT files only to control selection). Let me see if the RULES tab code is properly processing the SID MGMT lists when populating the drop-down.
Probably another consequence of the PHP 8.1 changes is my first guess.
Updated by Bill Meeks over 2 years ago
- File Emerging_DNS_category.png Emerging_DNS_category.png added
- File SID_MGMT_Emerging_DNS_enabled.png SID_MGMT_Emerging_DNS_enabled.png added
Still working for me in an existing installation. I just went to the SID MGMT tab, created an enablesid.conf file, and put the "emerging-dns" rules category in it, assigned it to the WAN interface instance, and saved (with the rebuild rules option checked at the bottom of the SID MGMT tab when saving). Then went direct to the CATEGORIES tab to verify the "Emerging-DNS" rules were auto-enabled (see the green "A" symbol in the screenshot), then went to the RULES tab and verified they were listed in the drop-down selector and could be loaded and viewed. See the attached two screenshots. Previously, on this WAN instance, that category was not enabled.
Give me a bit and I will wipe out this Suricata installation completely and install a new greenfield setup from scratch and try to reproduce what you are seeing.
Updated by Bill Meeks over 2 years ago
A fresh greenfield install still works for me, showing the rule categories auto-enabled on the CATEGORIES tab (green "A" icon beside the name), and then showing the correct category names in the drop-down selector on the RULES tab. I just updated my VM to the latest December 26 DEVEL snapshot and installed the Suricata-6.0.8_3 GUI package.
Prior to this I had completely wiped the existing Suricata config by selecting the option to "not save config when de-installing", and then removed the package and all the previous setup's log files. So I started with a totally empty Suricata setup.
The only difference I see in my current test configuration is that I have not auto-disabled the built-in "events" rules that ship with Suricata. I see in your screenshot that those are apparently auto-disabled via SID MGMT (as they appear to have a red "A" beside the names). I will try that next to see if that might have a bearing on the outcome.
Updated by Bill Meeks over 2 years ago
Okay, was able to reproduce the condition when using SID MGMT to auto-disable rules. Will dig into the processing to see what's happening and then get a fix submitted.
Updated by Bill Meeks over 2 years ago
This issue is corrected by Pull Request 1210 submitted to the DEVEL branch: https://github.com/pfsense/FreeBSD-ports/pull/1210.
This issue can be marked as resolved when the pull request is merged.
Updated by Jim Pingle over 2 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
PR Merged.