Snort-dev has been released. old snort has been renamed snort-old
-
tester_02 do me a fav. deinstall snort and then install again.
I forgot are you on 2.0 ?I added code that removes snort-old entries. It should help your deinstall problems.
If it does not report back here as soon as you can.I working out these problem on a pfsense 1.2.3 nanobsd on a CF card
every thing seems fine.James
-
Hi,
I am using PfSense 1.2.3.
I confirm that the latest snort package version 1.20 is working correctly!Thanks a lot for the fix jamesdean and i hope that you can keep up the excellent work ;)
Kind regards,
David Negreira. -
Hi JamesDean,
I have the latest Snort running and i am noticing something.i had Snort working fine with one interface up (WAN)
At one point, i needed to disable Snort….So i disabled Snort on the WAN interface (only interface i configured), but Snort still is/was blocking.
Snort Service was still started in Services (which it would seem correct since one interface should not stop the whole package)I'm i missing a setting or something?
Thanks for your help
Also, would you rather new threads on issues or continue this thread?
Again, thanks for the work on this package!PF 1.2.3 Full
Snort 2.8.5.3 pkg v. 1.19 -
Vito,
Try to install the latest snort package 1.20.
-
ok… did that just come out?
I thought i checked yesterday.anyway, just installed....Now all my settings are gone....
-
Hi,
I am using PfSense 1.2.3.
I confirm that the latest snort package version 1.20 is working correctly!Does it mean that upgrade from previous Snort package is now possible without full pfSense reinstall?
-
Hi,
I am using PfSense 1.2.3.
I confirm that the latest snort package version is working correctly!Does it mean that upgrade from previous Snort package is now possible without full pfSense reinstall?
Yes it does mean that.
I can also confirm that this release works without full Pfsense reinstall. I was stuck with the old snort installation version untill 1.20 was released.
The 1.20 version seems to have some minor bugs left (update rules page only works with Firefox and stays stuck with "please be patient" message eaven when using Firefox after the rule update is finnished, and in my case it took a while before snort started actually blocking those hosts that generate alerts), but these are not big issues in my opinion.
-
Snort 1.20 install went great, no issues on my 1.2.3.release install. I had no issues on my firefox and getting new rules.
Can others comment if they do an upgrade from the old releases (2.8.4 v1.7) that their installs do work? Also, if you deinstalled, and then installed the new package, or just did a reinstall to upgrade?
I have my brothers update to do, and don't want to do a reinstall as he is not local to me and he's completely new to pfsense. :)
-
Snort 1.20 install went great, no issues on my 1.2.3.release install. I had no issues on my firefox and getting new rules.
Can others comment if they do an upgrade from the old releases (2.8.4 v1.7) that their installs do work? Also, if you deinstalled, and then installed the new package, or just did a reinstall to upgrade?
I have my brothers update to do, and don't want to do a reinstall as he is not local to me and he's completely new to pfsense. :)
The best now is after a reboot it uninstalls it's self .great fix that was .
-
Snort 1.20 install went great, no issues on my 1.2.3.release install. I had no issues on my firefox and getting new rules.
Can others comment if they do an upgrade from the old releases (2.8.4 v1.7) that their installs do work? Also, if you deinstalled, and then installed the new package, or just did a reinstall to upgrade?
In my case (runnig pfsense 1.2.3 and the old snort version was 2.8.4 v1.7). I did deinstall the old version first and then installed the new 1.20 package. Worked fine that way
Just in case for those that are doing upgrade, or new with snort : Also remeber tho check the preprocessors settings when activating new rules. Snort wont start if you activate rules that require for example http preprocessor and the needed preprocessor is not selected (snort logs are good for finding what is wrong).