Snort 2.9.2.3 pkg v. 2.5.0 Issues

[dwood]

I have two installations working fine, (2.0.1) and autoupdates set for every six hours for testing.  So far so good..however the error may return when the rules are actually updated.  I suspect that there are no new rules yet which would have triggered an actual update.

EDIT:  Yep, an update (emerging threats) triggered same error.  Removed, erased snort bits, reinstalled and started fine.  Turned off updates for now.  The good news is that snort is behaving and blocking just fine otherwise :-) Thanks Ermal.

Btw, the WAN blocking issue has not re-occurred on two AMD64, 2.0.1 installations.  Important to note that snort should be uninstalled, then run "find /* | grep -i snort | xargs rm -rv" , then reinstall.  This ensures you get a new SNORT binary..at least for now, reinstalling won't replace the SNORT binary file.

Cheers,
Dennis.

[eri--]

Should behave better if you just reinstall.
No new binary needed.

[judex]

After reinstall I got

FATAL ERROR: /usr/local/etc/snort/snort_4672_em1/preproc_rules/preprocessor.rules(202) Unknown ClassType: sdf

After complete reinstallation snort rules download failes. Not even the md5 file gets downloaded.

php: /snort/snort_download_rules.php: Snort rules file downloaded failed…

Maybe snort server is down...but I get message that there is a new set available.

EDIT: 7 hours later and after another reinstallation snorts starts up without error and snort.org rules were downloaded. Everything seems to work so far...

[aaronritter]

Can anyone tell why this is missing after auto rule update:

added the line: config classification: sdf,Sensitive Data was Transmitted Across the Network,2
At the end of: /usr/local/etc/snort/classification.config

[mschiek01]

@ermal:

Should behave better if you just reinstall.
No new binary needed.

Ermal this is still not working.  I reinstalled the latest. downloaded the rules clicked start same error as before.

bad-traffic.so is not selected in snort rules.

Jul 18 19:44:28 snort[50712]: FATAL ERROR: Failed to load /usr/local/lib/snort/dynamicrules/bad-traffic.so: /usr/local/lib/snort/dynamicrules/bad-traffic.so: Undefined symbol "freeRuleData"
Jul 18 19:44:28 snort[50712]: FATAL ERROR: Failed to load /usr/local/lib/snort/dynamicrules/bad-traffic.so: /usr/local/lib/snort/dynamicrules/bad-traffic.so: Undefined symbol "freeRuleData"
Jul 18 19:44:28 snort[50712]: Loading dynamic detection library /usr/local/lib/snort/dynamicrules/bad-traffic.so…
Jul 18 19:44:28 snort[50712]: Loading dynamic detection library /usr/local/lib/snort/dynamicrules/bad-traffic.so…
Jul 18 19:44:28 snort[50712]: Loading all dynamic detection libs from /usr/local/lib/snort/dynamicrules…
Jul 18 19:44:28 snort[50712]: Loading all dynamic detection libs from /usr/local/lib/snort/dynamicrules…
Jul 18 19:44:28 snort[50712]: Finished Loading all dynamic engine libs from /usr/local/lib/snort/dynamicengine
Jul 18 19:44:28 snort[50712]: Finished Loading all dynamic engine libs from /usr/local/lib/snort/dynamicengine
Jul 18 19:44:28 snort[50712]: WARNING: No dynamic libraries found in directory /usr/local/lib/snort/dynamicengine.
Jul 18 19:44:28 snort[50712]: WARNING: No dynamic libraries found in directory /usr/local/lib/snort/dynamicengine.
Jul 18 19:44:28 snort[50712]: Loading all dynamic engine libs from /usr/local/lib/snort/dynamicengine…
Jul 18 19:44:28 snort[50712]: Loading all dynamic engine libs from /usr/local/lib/snort/dynamicengine…

[tester_02]

It's so close now…  I'm still on 2.9.1 and waiting for the list of issues to die down and I can see it's almost there.   
Just wanted to thank all Ermal AND all the users doing the testing.  Everyone's help is appreciated by the rest of us.

[Cino]

^^^ he was the smart one  ::)

all my testing is on my home box, so i dont care if it breaks here and there… now the wife on the other hand is a different story... But she is best user tester... I know within seconds if the internet is down... In this case, snort blocking facebook or pinterest because it didn't like the http packets that were sent over..

[mschiek01]

@Cino:

@ermal:

Should behave better if you just reinstall.
No new binary needed.

I couldn't wait for my box to auto update but wanted to test your changes before i leave for my annual military training. So I ran the the cron job from shell and seems to work.. It downloaded a new set of rules and started snort… I love the fact now we dont have to download a new ruleset went we do a reinstall.. Thank you again!!!

/root(1): /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_for_rule_updates.php >> /tmp/snort_update.log
rm: /usr/local/etc/snort/snortrules: No such file or directory
/root(2):

P.S I sent a small donation in today for beer  ;D

Are you sure when you ran the rule update there was indeed an update downloaded?

[dwood]

Ermal, reinstalled (AMD64, 2.0.1) and got this:

Jul 18 22:04:22 snort[23595]: FATAL ERROR: Failed to load /usr/local/lib/snort/dynamicrules/bad-traffic.so: /usr/local/lib/snort/dynamicrules/bad-traffic.so: Undefined symbol "freeRuleData"
Jul 18 22:04:22 snort[23595]: Loading dynamic detection library /usr/local/lib/snort/dynamicrules/bad-traffic.so…

However, an uninstall, manual delete, and reinstall worked.  Will set to autoupdate and see what happens.

[digdug3]

Had the same issues with auto-update. I didn't reinstall, but just updated manually and the manually restarted the Snort interface(s).
This worked for me this time. Will disable auto-update in the meanwhile.

[Cino]

@mschiek01:

@Cino:

@ermal:

Should behave better if you just reinstall.
No new binary needed.

I couldn't wait for my box to auto update but wanted to test your changes before i leave for my annual military training. So I ran the the cron job from shell and seems to work.. It downloaded a new set of rules and started snort… I love the fact now we dont have to download a new ruleset went we do a reinstall.. Thank you again!!!

/root(1): /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_for_rule_updates.php >> /tmp/snort_update.log
rm: /usr/local/etc/snort/snortrules: No such file or directory
/root(2):

P.S I sent a small donation in today for beer  ;D

Are you sure when you ran the rule update there was indeed an update downloaded?

Looks like I spoke too soon, check again this morning. And it failed

[judex]

At the moment snort ist working ok.

Autoupdates fail but snort keeps on snorting on my system.

Manual update works, if I delete snortrules MD5 file before.

WAN blocking does not occur any more.

Greets, Judex

[mdima]

@judex:

WAN blocking does not occur any more.

Hi, I was updating this morning, few hours ago, and my WAN IPs were still get blocked (block: Both), even if they are on the whitelist (both choosing a whitelist then leaving "default" as whitelist)…

Thanks,
Michele

[breusshe]

@mschiek01:

Ermal this is still not fixed.

If snort is running and downloads a new rule update then tries to apply it, the same will occur. I have the latest version update.  Of course if I uninstall snort and reinstall it will start again and run fine but it is still not fixed as the next rule update will cause the same error.

Jul 18 12:19:33 snort[31831]: FATAL ERROR: /usr/local/etc/snort/snort_27588_em1/preproc_rules/sensitive-data.rules(1) Unknown ClassType: sdf
Jul 18 12:19:33 snort[31831]: FATAL ERROR: /usr/local/etc/snort/snort_27588_em1/preproc_rules/sensitive-data.rules(1) Unknown ClassType: sdf
Jul 18 12:19:33 snort[31831]: Initializing rule chains…
Jul 18 12:19:33 snort[31831]: Initializing rule chains…
Jul 18 12:19:33 snort[31831]: +++++++++++++++++++++++++++++++++++++++++++++++++++
Jul 18 12:19:33 snort[31831]: +++++++++++++++++++++++++++++++++++++++++++++++++++

I'm still getting this too.  I delete the md5 files and redownload the snort rules, snort starts fine after that.  But, next time new rules are downloaded, I'll get this error again.

[Fesoj]

Hi,

I am just curious about how you are updating (System packages or Git repository). The regular package update is about 2 days old, but ermal has updated the sources since then.

A quick check to find out what you are running is to check select the "Rules" tab of one of the snort interfaces. If there is visual glitch on top of the page, then you are still running an "old" version.

I had some of the messages reported here a couple of days ago, but not lately. If someone is not sure what is currently installed a diff -u for a candidate file (e.g. snort.inc) and the corresponding one from https://github.com/bsdperimeter/pfsense-packages/tree/master/config/snort should clarify the situation.

[marcelloc]

Fesoj,

When you see updates on git and/or announces on forum, just wait 15 minutes after the update date-time and then re-install the package.

att,
Marcello Coutinho

[mschiek01]

@Fesoj:

Hi,

I am just curious about how you are updating (System packages or Git repository). The regular package update is about 2 days old, but ermal has updated the sources since then.

A quick check to find out what you are running is to check select the "Rules" tab of one of the snort interfaces. If there is visual glitch on top of the page, then you are still running an "old" version.

I had some of the messages reported here a couple of days ago, but not lately. If someone is not sure what is currently installed a diff -u for a candidate file (e.g. snort.inc) and the corresponding one from https://github.com/bsdperimeter/pfsense-packages/tree/master/config/snort should clarify the situation.

You are correct that latest code does appear to have solved the issue.  But it has not been added to the package as of yet. I manually added it and it is working.

[Fesoj]

Marcello,

When you see updates on git and/or announces on forum, just wait 15 minutes after the update date-time and then re-install the package.

yes, I do know that. It just looks to me that some of the current posts relate to older versions of snort and not to the up to date version in the repository.

BTW, if someone is interested, I have a short quick&dirty script that checks whether the binary package from files.pfsense.org has been updated, since the version string does not necessarily get updated. If there's any interest, I'll post it.

[dwood]

Fesoj..thanks for posting that information.  I've been slowly collecting bits and pieces of the github process into my grey matter..your post helps.  It would be helpful to me and no doubt others if you could post a "Github and SNORT for Dummies".  This would certainly help out with more detailed feedback in the troubleshooting process for Ermal.  I would be interested in that script :-)

I believe another issue here is that reinstalling SNORT over an existing version is behaving differently (depending on what got sync'd) than first uninstalling -> deleting leftover bits -> and reinstalling.  Over the last year of messing with SNORT the clean install has become my standard install to avoid the issue of troubleshooting leftover files/code/configuration.

[Fesoj]

Here it is:

#!/bin/sh
DLURL=http://files.pfsense.com/packages/8/All
SNORT=snort-2.9.2.3-i386.pbi.sha256
if [ -e $SNORT ]; then
  mv -f $SNORT $SNORT.bak
fi
echo "Getting $DLURL/$SNORT"
wget "$DLURL/$SNORT"
echo 
echo

if [ -e $SNORT ] && [ -e $SNORT.bak ]; then
  delta=`diff -q $SNORT $SNORT.bak`
  if [ -n "$delta" ]; then
    echo "+------------------+"
    echo "| Update available |"
    echo "+------------------+"
  else
    echo "+---------------------+"
    echo "| No update available |"
    echo "+---------------------+"
  fi
fi

The script does not update anything and it needn't be on the pfSense box. It just reports about an update between subsequent calls. Strictly speaking it is valid only for pfSense 2.1, but the *.tbz files typically get updated about the same time (give or take an hour, or so).