jackbenny/quick_fix_pfsense
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Validation fix

Browse Source
This commit is contained in:
Jack-Benny Persson 2012-05-08 04:36:20 +02:00
parent 0dbdeb4751
commit 3a1339fb36
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
quick_fix.html
View File

@ -17,7 +17,7 @@ Jack-Benny Persson
<i>Originaly posted in the pfSense forum on 2012-04-17</i> <i>Originaly posted in the pfSense forum on 2012-04-17</i>
</b> </b>
<br /> <br />
<br /> </p>
<table border = "1"> <table border = "1">
<caption>Revision history</caption> <caption>Revision history</caption>
<tr> <tr>
@ -39,7 +39,6 @@ Jack-Benny Persson
<td>jackbenny</td> <td>jackbenny</td>
</tr> </tr>
</table> </table>
</p>
<p> <p>
I started using the Snort package for pfSense 2.0.1 (amd64) some days ago but as many others I noticed the problem with the enable/disabled rules resetting after updating the rules.<br /> I started using the Snort package for pfSense 2.0.1 (amd64) some days ago but as many others I noticed the problem with the enable/disabled rules resetting after updating the rules.<br />
So last night I started working on a quick fix for it, and came up with a nice and working solution. My solution involves enabling and disabling specific rules in a oinkmaster.conf file, so it&#039;s not a GUI solution. But at least now it&#039;s possible to have your own set of enabled/disabled rules.<br /> So last night I started working on a quick fix for it, and came up with a nice and working solution. My solution involves enabling and disabling specific rules in a oinkmaster.conf file, so it&#039;s not a GUI solution. But at least now it&#039;s possible to have your own set of enabled/disabled rules.<br />