Snort 2.9.5.5 pkg v3.0.1 Update – Minor bug fixes
-
-
It also looks like my Snort interfaces now start much faster?!
-
It also looks like my Snort interfaces now start much faster?!
That could be a 2.9.5.5 Snort binary benefit. There is really nothing that changed in the GUI code that should impact that. I noticed that my interfaces also seem to start faster. Of course I also recently updated my hardware from an Atom to an Intel i3 3.3 GHz processor, so that may also have a lot to do with it on my end.
Bill
-
Hi,
when installing this package I get this error:
snort[44829]: FATAL ERROR: The dynamic detection library "/usr/pbi/snort-amd64/lib/snort/dynamicrules/lib_sfdynamic_example_rule.so" version 1.0 compiled with dynamic engine library version 1.0 isn't compatible with the current dynamic engine library "/usr/pbi/snort-amd64/lib/snort/dynamicengine/libsf_engine.so" version 1.17.
I have tried to uninstall, reboot and install several times with no luck.
-
Hi,
when installing this package I get this error:
snort[44829]: FATAL ERROR: The dynamic detection library "/usr/pbi/snort-amd64/lib/snort/dynamicrules/lib_sfdynamic_example_rule.so" version 1.0 compiled with dynamic engine library version 1.0 isn't compatible with the current dynamic engine library "/usr/pbi/snort-amd64/lib/snort/dynamicengine/libsf_engine.so" version 1.17.
I have tried to uninstall, reboot and install several times with no luck.
This generally indicates an old copy of the shared object rules around someplace. I'm surprised because this shouldn't happen on 2.1 pfSense with PBI. Tell me if this was originally a 2.0.x box upgraded to 2.1.
As for the fix, try these steps.
-
Remove the Snort package by clicking the X icon beside the Snort package on the Installed Packages tab.
-
When the package deletion completes, open a console session to the firewall and exit to the shell prompt. Type the command rm -rf /usr/local/lib/snort
-
Now install Snort again by going to Available Packages and choosing it.
If you still have trouble, then gather some troubleshooting information for me. From a console session, issue the command:
snort -Vand tell me what version it prints.
Bill
-
-
Snort Alerts list doesn't show entries from 1.1.2014 at the top. When clicking on the Date column to sort by date, the alerts from today show up at the top again. Bug or by design?
-
It does here on all firewalls. (show entries from 01/01/14)
Running 2.0.3 with the latest Snort.
-
Same here "fragged" on 2.1 x64. I'm sure within the next day all will be fine.
-
On a closer look no matter how I arrange by date, it's always backwards for 2014 vs 2013. Must be a bug in the sorting piece of code or something.
-
… and the problem flows through to the Dashboard Widget, resulting in the most current alerts not being displayed.
-
As said….not an issue on 2.0.3 for me.
-
On a closer look no matter how I arrange by date, it's always backwards for 2014 vs 2013. Must be a bug in the sorting piece of code or something.
I checked on my production firewall and indeed the default sort appears to be putting the December 31, 2013 events above the January 2014 events. However, you can click the DATE column header on the Alerts tab and sort the alerts so the January 01, 2014 events are at the top. See the screenshot below showing the sorted list. This is from a 2.1-RELEASE pfSense firewall.
Bill
-
On 2.0.3 it seems fine Bill.
-
On 2.0.3 it seems fine Bill.
OK. I just edited/replaced my original reply above with updated info. I will check the Dashboard Widget next on 2.1.
Bill
-
OK, found a "sort of fix" for the Snort Alerts Dashboard Widget. It keys off the "sort setting" for the System Log. If you have your system log entries displaying in reverse order, then the Snort Alerts Widget sorts the same way. If you toggle System Log entries to display in "normal order", then the Snort Alerts Widget sorts correctly.
The problem here is, I think, in the sorting logic of the System Log. When toggled to display in "reverse" (that is, newest entries displayed first), it sorts the leading zero improperly in the timestamp. The same problem is copied over into the Snort Widget code by the original author.
Bill
-
The log in Snort on the alerts table has the problem even on 2.0.3.
The widget doesnt.
-
The log in Snort on the alerts table has the problem even on 2.0.3.
The widget doesnt.
Fixing the sorting will take a little extra magic to handle the leading zero or one in the months. Sorting as a plain string won't work. I will see if I can make it smarter.
Bill
-
Fixing the sort turned out to be easier than I thought it would. I fixed both the ALERTS tab display and the Snort Alerts Widget. Let me test a wee bit more to be sure there are no unintended consequences from the fixes, then I will submit a Pull Request for a minor update to the Snort package and the Dashboard Alerts Widget.
Bill
-
When doing so Bill, cant you try to import the code from the traffic graph widgets since they have an interval function built in to update the Snort alert widget without refreshing the whole page…
-
When doing so Bill, cant you try to import the code from the traffic graph widgets since they have an interval function built in to update the Snort alert widget without refreshing the whole page…
Well, it's too late for this Widget fix. Ermal merged the update this morning. The current widget should be updating every 22 seconds if I understand the code correctly. I think jimp originally wrote it. His name is in the copyright info at the top of the source code.
There also may be a problem with the older 2.0.3 pfSense code with respect to JavaScript callbacks for the active refresh. Not sure, though. I will test on my 2.1 install to see if it auto-refreshes the Snort Alerts frame.
Bill
