Problem SNORT 2.9.1 pkg v. 2.1
-
Hi,
I don't understand why you can specify which IP to block (src, dst, both) only if your HomeNet is a "whitelists" and not a "netlist".
Can you pls tell me the reason?I see the "Which ip to block" select empty… Anyway, in this case what happens?
Thanks,
Michele -
binaries seem to be in but there are some issues..
@emarl The GUI doesn't have anything for the "Which ip to block" field under If Setting. Going to see if I can manually edit the conf file and see if I can get it to start when i have block offenders enabled.
Again is ermal.
Fixed.
-
is it safe to use the gui package management to upgrade now?
-
@ermal:
binaries seem to be in but there are some issues..
@emarl The GUI doesn't have anything for the "Which ip to block" field under If Setting. Going to see if I can manually edit the conf file and see if I can get it to start when i have block offenders enabled.
Again is ermal.
Fixed.
Hi Ermal,
thanks for fixing. Unfortunately now when I start the service I get the errors:FATAL ERROR: pf.conf => Table snort2c,src,kill don't exists in packet filter
or
FATAL ERROR: pf.conf => Table snort2c,dst,kill don't exists in packet filter
or
FATAL ERROR: pf.conf => Table snort2c,both,kill don't exists in packet filterdepending on what option I set in the "Which ip to block" field of the interface…
Thanks,
Michele -
is it safe to use the gui package management to upgrade now?
I would wait a while…. I am doing my test on my secondary machine and I am having some trouble...
-
mdima,
EDIT: it seems you nave installed old binary still on your system that is why you get the error
-
@ermal:
mdima,
your options tells that you do not have a table snort2c defined in your filter rules.
Which should be by default hardcoded on pfSense rules.
Can you check on /tmp/rules.debug that there is a <snort2c>table defined?</snort2c>Hi Ermal,
thanks for your prompt answer.The table is defined in /tmp/rules.debug ("table <snort2c>" at line 15) and I can also see it in the Diagnostic->Tables page…
Thanks,
Michele</snort2c> -
@ermal:
mdima,
EDIT: it seems you nave installed old binary still on your system that is why you get the erroryes, even updating the package didn't help. So I removed then reinstalled the package and now everything seems to work… I will update my primary machine now and test it in deep!
Thanks,
Michele -
There are 2 buttons there for re-installing a package.
One just installs the php code and the other updates the binaries as well.I can only assume that you clicked the wrong button.
-
@ermal:
There are 2 buttons there for re-installing a package.
One just installs the php code and the other updates the binaries as well.I can only assume that you clicked the wrong button.
mmhhh… no, I pressed the "full reinstall" ("pkg icon"), not only the "interface" ("xml icon"), I am pretty sure because I did it twice after your message and I verified that pfSense didn't download the binary files...
-
Thanks again to Ermal, Cino and Catfish. I learned a lot more about pfsense, particularly github and the code update process this time around :-)
I removed, then reinstalled (with settings saved) and everything seems to be working well. As always, rules must be updated after an update…no issues there. I've enabled "block offenders" "Kill states" and Block "SRC" and everything fired up (including a full set of rules) just fine. Version is AMD64, PF 2.0.1
Cheers,
Dennis. -
Ok, so before when I updated, I could not get snort to start after I selected block offenders, after updating again, I was able to get snort to start with block offenders checked, but now when I select any category, even if I select 1 freaking category, save and then try to restart snort, it will not start. "WTF" Thank God I have an Untangle system on the backend doing IPS.
-
Update on the start issue. I found that the preprocessor section needs to be saved again. Click the save button and then make sure you have http inspect checked and then place a -1 in the HTTP server flow depth field to disable it, then click save one more time. After that I was able to get SNORT to finaly start with blocking and rules selected.
-
This was not required here. Did you have "Keep snort settings after deinstall" checked off in Global settings before you uninstalled SNORT? Were your rules categories settings saved?
Cino et al, are you seeing lower memory usage? At AC-BNFA, memory usage seems to have dropped 10 to 20 percent.
-
Yeah, why would I want to recreate everything, I don't see anyway of exporting my 100 plus entries WhiteList without wincp into my pfsense box. The fact that I would have to clear my config in order to update to a newer version of SNORT is ridiculous. No other open source firewall or UTM I know of using SNORT requires this.
-
Note: might want to look at this category snort_file-identify.rules
Seems to cause starting issues as well.
-
Awesome Snort is now working beautifully!
Thanks ermal!
Also, just as a note, I also still need to add 'portvar FILE_DATA_PORTS [$HTTP_PORTS,110,143]' in order to get Snort to start on AMD64.
Thanks again!
-th3r3isnospoon
-
@ermal sorry about that again…I thought I checked the spelling.. Anyways your latest changes fixed the which ip to block option. I'm able to get snort to start with this option and with/and without Kill option enabled.. I'm thinking portvar FILE_DATA_PORTS [$HTTP_PORTS,110,143] just needs to be added to the snort.inc file somewhere?
You mention about the 2 install options, I've meant to bring this up awhile going for some reason both options seem to do the same thing on my box.. Doesn't matter what package… if I want to just have the xml update, it removes the binaries and tries to installed them again( which doesn't work but its because i'm running 2.1-dev so i know the work around)
As always Ermal, thank you again for the quick fixes!
@dwood I am seeing about 10% difference.. I also use AC-BNFA... Have to put it to the test over the weekend.
@everyone Search the forum... After every reinstall of snort, you need to update rules.. then go to every page within the interface and click save. I know its a pain but this will ensure that the settings that are in your config.xml are synced to the snort.conf file.
-
Hello Everybody!
after some initial issues, uninstalling and reinstalling the package it worked! And it is working GREAT!!The main problem I had was the block of the offenders even when they were the "destination IP", and this is working!
Thanks to Ermal for the fixes and support!!
Michele
-
For whatever reason I did not have to add portvar FILE_DATA_PORTS [$HTTP_PORTS,110,143] to get SNORT 2.1.1 started and blocking with all rules. (AMD64)
I did however uninstall a few days ago with no settings saved, rebooted..and deleted any snort directories left over before installing the new version.