Bug #10917
closed
snort: invalid pidfile suffix error
Added by Anonymous over 4 years ago.
Updated over 4 years ago.
Affected Version:
2.4.5-p1
Affected Architecture:
All
Description
After upgrading snort package from 3.2.9.14_1
to 4.1.2
, I have two interfaces where snort gives the following error:
Sep 19 02:30:20 10.69.22.1 SnortStartup[50931]: Snort START for WLAN_DMZ(ath0_wlan1)...
Sep 19 02:30:20 10.69.22.1 snort[51238]: FATAL ERROR: Invalid pidfile suffix: _ath0_wlan1. Suffix must less than 11 characters and not have ".." or "/" in the name.
Sep 19 02:30:20 10.69.22.1 SnortStartup[51690]: Snort START for WLAN_HA(ath0_wlan3)...
Sep 19 02:30:20 10.69.22.1 snort[51726]: FATAL ERROR: Invalid pidfile suffix: _ath0_wlan3. Suffix must less than 11 characters and not have ".." or "/" in the name.
Related bug: #692
Thanks.
According to the pfsense forum, the developer of the snort package (thanks bmeeks) is aware of the bug and will fix it soon.
This issue also impacts the Snort package on pfSense-2.5 under the same conditions when the physical interface name and any associated VLAN IDs exceed 11 characters in length.
A fix has been identified and testing is underway to ensure there are no other unintended side effects. I will post an update when the fix is deployed as a Pull Request against the two pfSense branches (RELEASE and DEVELOPMENT).
Two pull requests have been submitted against pfSense-2.4.5 and pfSense-2.5 to fix the issue reported in this ticket. The requests are awaiting review and merging by the pfSense developer team.
- Status changed from New to Pull Request Review
- Status changed from Pull Request Review to Feedback
- Assignee set to Renato Botelho
- % Done changed from 0 to 100
PR has been merged. Thanks!
The pull requests against pfSense-2.4.5-RELEASE and pfSense-2.5-DEVELOPMENT have been merged. This issue can be marked RESOLVED.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF