Snort Stable 2.9.2.3 pkg v. 2.2 Failed

mschiek01

services/snort
click to edit the interface in question
Select the Catagories tab
Select the rules you want to use.

Do not select any of the .so "shared objects rules" they will cause snort to crash.

From your description it sounds like you don't have any rules selected.

fragged

I have tried with and without rules enabled. Currently I have only EM rules installed and 2 of them selected. Still I don't get anything useful on the system log.

mschiek01

On the Interface tab
general you have enabled the interface correct?

on the same tab under
Choose the types of logs snort should create.
you selected "Send alerts to main System logs"

On the preprocessors tab you have enabled "performance statics for this interface"

If all else fails you could try running this command from the console comand line although I do not think this is the problem

pkg_add -f http://files.pfsense.org/packages/8/All/snort-2.9.2.3.tbz

Then update your rules and try to start snort.

johnnybe

@ermal:

Its fixes so just reinstall.

It's running here 2.0.1-RELEASE (amd64) and kept all previous settings. All that I did, after reinstall, was to update ET rules.

pfnewbe

@caustic386:

To get this to work, I had to uninstall, then run the following:

pkg_delete -f snort*
find / -name snort

and rm -rf anything that turned up. Reinstalling with new package fixed it from there, running snort rules and ET.

This worked for me!
Tnx

miles267

Has anyone else noticed on their Snort > Blocked (tab) that the ALERT DESCRIPTION next to each IP now says "N/A" instead of displaying a full description as it has in the past?

I've confirmed under Snort > Global Settings, my Alert file description type = FULL.

Is there any way to restore this functionality so that full alert description is listed?

mschiek01

I think it is now being shown under the Alerts/Interface tab.

Have you noticed if the blocked ip's are being removed in the time you have specified?

miles267

The alert info has always been displayed within the Snort > Alerts tab. But requires excessive searching to find the info that corresponds with a blocked IP. Whereas, on the BLOCKED tab, it used to specifically show the ALERT DESCRIPTION that corresponds with each blocked IP. More straight forward.

No - I've not yet confirmed that the blocked IPs are expiring within the interval I've configured. I've been having to clear and reset snort blocks constantly to keep snort running so it's been somewhat of a moving target.

Wish the latest snort was more stable. Though I'm sure most of my issues are already being addressed for subsequent release.

digdug3

@pfnewbe:

@caustic386:

To get this to work, I had to uninstall, then run the following:

pkg_delete -f snort*
find / -name snort

and rm -rf anything that turned up. Reinstalling with new package fixed it from there, running snort rules and ET.

This worked for me!
Tnx

Got snort working again (AMD64). EM and Snort rules.
Indeed, just remove the package first and then reinstall it.

eri--

@miles267:

Wish the latest snort was more stable. Though I'm sure most of my issues are already being addressed for subsequent release.

Stable in what sense? And how you know will be addressed in the future? :)

This is infuriating. How come everytime a snort update is release that pfSense is totally incapable of doing an upgrade that doesn't completely break it and requiring people to wipe their snort config and reinstall? I keep getting so close to pitching this for our enterprise but then crap like this happens perpetually. What kind of QA, if any, is being done? One virtual machine or box and then it gets signed off? That's what it feels like. If a simple package update can't be properly scripted and automated why would someone buy commercial support?

Cino

@mschiek01:

I think it is now being shown under the Alerts/Interface tab.

Have you noticed if the blocked ip's are being removed in the time you have specified?

It does for me… make sure you save the global page.. this creates the cron job for it

digdug3

@Cino:

@mschiek01:

I think it is now being shown under the Alerts/Interface tab.

Have you noticed if the blocked ip's are being removed in the time you have specified?

It does for me… make sure you save the global page.. this creates the cron job for it

I have the same problem. Saved the global page, still the blocked ip's aren't removed.
AMD64 version. Two interfaces.

mschiek01

@Cino:

@mschiek01:

I think it is now being shown under the Alerts/Interface tab.

Have you noticed if the blocked ip's are being removed in the time you have specified?

It does for me… make sure you save the global page.. this creates the cron job for it

Thanks for the tip the cron job was there but must not have been running correctly. I changed the setting to never then saved, then changed back to 1 hour and saved again. It is now working.

Now if I could just figure out why snort stops working after a couple of hours. It is doing this on multiple boxes.

digdug3

Thanks for the tip, will try it and post back.

eri--

@mschiek01:

Now if I could just figure out why snort stops working after a couple of hours. It is doing this on multiple boxes.

Can you give me any log entries about this.

eri--

@snadsnad:

This is infuriating. How come everytime a snort update is release that pfSense is totally incapable of doing an upgrade that doesn't completely break it and requiring people to wipe their snort config and reinstall? I keep getting so close to pitching this for our enterprise but then crap like this happens perpetually. What kind of QA, if any, is being done? One virtual machine or box and then it gets signed off? That's what it feels like. If a simple package update can't be properly scripted and automated why would someone buy commercial support?

Well there is something in the enterprise called patch management process that shuold be done before allowing these things to production.
A testbed is not so much costy for pfSense in general as well.

While i do agree that this upgrade was not correct, you have to keep in mind that the code of the snort package is by no means finished and up-to 5 minutes ago it had code that removed critical components of snort on just reinstall!!!

Anyway we are trying hard to improve the process and locking some packages as such but community need to support as well with any means.
Also comercial support will give you support on any issue you will have be it snort/pfSense/or your rant :).

eri--

@miles267:

Has anyone else noticed on their Snort > Blocked (tab) that the ALERT DESCRIPTION next to each IP now says "N/A" instead of displaying a full description as it has in the past?

I've confirmed under Snort > Global Settings, my Alert file description type = FULL.

Is there any way to restore this functionality so that full alert description is listed?

It should work on latest version 2.2.1

mschiek01

@ermal:

@mschiek01:

Now if I could just figure out why snort stops working after a couple of hours. It is doing this on multiple boxes.

Can you give me any log entries about this.

I for one appreciate your efforts.
I will send you some logs as soon as snort stops again. I am hoping though that the issue with the cron job not removing the blocked ip's had something to do with it, this is just a guess for now.
Thanks for your hard work.

mschiek01

@ermal:

@snadsnad:

This is infuriating. How come everytime a snort update is release that pfSense is totally incapable of doing an upgrade that doesn't completely break it and requiring people to wipe their snort config and reinstall? I keep getting so close to pitching this for our enterprise but then crap like this happens perpetually. What kind of QA, if any, is being done? One virtual machine or box and then it gets signed off? That's what it feels like. If a simple package update can't be properly scripted and automated why would someone buy commercial support?

Well there is something in the enterprise called patch management process that shuold be done before allowing these things to production.
A testbed is not so much costy for pfSense in general as well.

While i do agree that this upgrade was not correct, you have to keep in mind that the code of the snort package is by no means finished and up-to 5 minutes ago it had code that removed critical components of snort on just reinstall!!!

Anyway we are trying hard to improve the process and locking some packages as such but community need to support as well with any means.
Also comercial support will give you support on any issue you will have be it snort/pfSense/or your rant :).

Ermal- The latest update is still deleting files and modules and not replacing them on reinstall.

/usr/local/lib/snort directories either missing or missing files

snort-2.9.2.3 "2.2.1" shows installed.