Snort Stable 2.9.2.3 pkg v. 2.2 Failed

taryezveb

Also as Cino points out..

http://forum.pfsense.org/index.php/topic,50397.msg268281.html#msg268281

noticed that too. barnyard2-1.9_2.tbz isnt built yet.. once its built, you should be good to go

smokes2345

you can download the package to your pfsense box from the pfsense repo using wget, then install with pkg_add (in my case it said it was already installed). The downside to this option is it only installs the command line tools, not the web configuration interface. To use it you will have to get familiar with the command-line options

Also, as mentioned previously, it's possible you might break something if you install from the standard freebsd repo. I would guess that risk is minimized if you install from the pfsense repo, but still possible if you install something intended for a different version than what you're using.

My install was failing while trying to install a dependency, barnyard2.
Downloading http://files.pfsense.org/packages/8/All/barnyard2-1.9_2.tbz … could not download from there or http://ftp2.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.1-release/All/barnyard2-1.9_2.tbz.
of barnyard2-1.9_2 failed!

tritron

There is http://files.pfsense.org/packages/8/All/barnyard2 file so maybe we can work around the issue fetch http://files.pfsense.org/packages/8/All/barnyard2 mv barnyard2 barnyard2-1.9_2.tbz then pkg_add -r barnyard2-1.9_2.tbz
What if for i386 we use http://mirrors.syringanetworks.net/pub/FreeBSD/ports/i386/packages-stable/security/barnyard2-1.9_2.tbz
or http://mirrors.syringanetworks.net/pub/FreeBSD/ports/amd64/packages-stable/security/barnyard2-1.9_2.tbz for 64 bit

eri--

Its fixes so just reinstall.

fragged

Snort 2.9.2.3 pkg v. 2.2 installs fine without errors, but after setting it up and updating rule files I get an error when I try to start it:

Snort HARD START For 62994_em0…

I currently only have EM rules selected.

2.0.1-RELEASE (amd64)
built on Mon Dec 12 18:16:13 EST 2011
FreeBSD 8.1-RELEASE-p6

Edit:
I tried to
1. Remove package + find /* |grep snort -> made sure no snort files are left over.
2. Rebooted pfsense
3. Installed Snort + configured it
4. Same error: Snort HARD START For 37895_em0...

I went through the same setup on a vm and I got it working without messing around with anything. Whats going on?

eri--

You are not showing your system log there.
There will be the cause of that.

I can expect missing pre processor.

sronsen

Finally, it appears that the updated package files and the snort updates are in synch and are working. However, the update seems to have broken the snort dashboard widget. It is not updating, although selecting on its header does open the snort alerts window. Tried removing and reinstalling the widget package to no effect.

Can someone verify this issue? Thanks.

Cino

@sronsen:

Finally, it appears that the updated package files and the snort updates are in synch and are working. However, the update seems to have broken the snort dashboard widget. It is not updating, although selecting on its header does open the snort alerts window. Tried removing and reinstalling the widget package to no effect.

Can someone verify this issue? Thanks.

it has… with the recently changes made to the alert page, the widget would probably have to be redone from scratch because the alerts are now broken out by interface, each interface has its own alert file now.....

sekular

I uninstalled snort when the install stopped working but my configurations saved across uninstalls. I installed it today and it went through fine. It loaded my previous configuration but no rules as expected (usually does this on updates). So i updated rules and disable and renable interface, checked all settings and enabled only one rule category to test. I get this error in syslog:

Jun 13 17:42:12 snort[37197]: FATAL ERROR: ByteExtract variable '^Authorization\x3A\sBasic[ \t]+' in rule [3:13308] is used before it is defined.
Jun 13 17:42:12 snort[37197]: FATAL ERROR: ByteExtract variable '^Authorization\x3A\sBasic[ \t]+' in rule [3:13308] is used before it is defined.

Should i wipe all the configurations and start from scratch ?

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.

mschiek01

Delete anything in this directory
/usr/local/lib/snort/dynamicrules
also uncheck any .so rules on your interfaces.

Try to start snort

sekular

That has resolved the problem. thanks.

fragged

@ermal:

You are not showing your system log there.
There will be the cause of that.

I can expect missing pre processor.

Status -> Servies -> Hit start on Snort, Status -> System log -> Jun 14 00:23:18 SnortStartup[18693]: Snort HARD START For 37895_em0… -is the only line generated.

If I try to run Snort from Services -> Snort -> Snort interfaces, I get two lines:

Jun 14 00:32:11 SnortStartup[35943]: Interface Rule START for 0_37895_em0…
Jun 14 00:32:11 SnortStartup[30175]: Toggle for 37895_em0…

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?