Snort 2.9.4.1 pkg v.2.5.8
-
Guys I updated and lost all my settings - no big deal but now I have an issue with http_inspect.
Constantly sites like google, reddit, imgur, yahoo, youtube…the list goes on... are getting blocked.
Can you please tell me what I am doing wrong with the setup of this and if any of you are seeing the same issues?
I tried to disable it via options but then snort won't start - guessing some WAN categories are dependent on http_inspect starting.
-
Just a small question regarding that….what if you change the 725px to 80% or 100% instead??
I am using 100% as the table widths, but when you call in the header and footer includes that constitute the pfSense GUI, you wind up running as a nested table that ends up being 100% of 725 pixels… :(
The good news is once something like the Widescreen package stabilizes and becomes part of the standard GUI, Snort should adapt quite well since all of its width specifications are in percentage.
Bill
-
Guys I updated and lost all my settings - no big deal but now I have an issue with http_inspect.
Constantly sites like google, reddit, imgur, yahoo, youtube…the list goes on... are getting blocked.
Can you please tell me what I am doing wrong with the setup of this and if any of you are seeing the same issues?
I tried to disable it via options but then snort won't start - guessing some WAN categories are dependent on http_inspect starting.
There is a check box on the Preprocessors tab at the bottom of the HTTP_INSPECT section that says "disable http_inspect alerts" or something similar. Tick that box. You should then no longer get blocks from HTTP_INSPECT alerts. There is also a new button at the bottom of the page for 2.5.8 that will reset all the preprocessor settings to their defaults. The default for HTTP_INSPECT should be enabled but with alerts disabled.
Attached below are my HTTP_INSPECT settings. You can also automatically add problem alerts to the Suppress List by clicking the plus icons (+) under the alert on the Alerts tab. Once you do this, you will need to stop and restart Snort to pick up the change.
Bill
-
Did you see the thread I created about finding a notification script by someone else? I am making good use of it. I only block on the LAN snort instance though. I would get too many notifications on the wan side.
http://forum.pfsense.org/index.php/topic,63418.0.html -
Did you see the thread I created about finding a notification script by someone else? I am making good use of it. I only block on the LAN snort instance though. I would get too many notifications on the wan side.
http://forum.pfsense.org/index.php/topic,63418.0.htmlYes, I saw the post. It is a handy script, but with a number of commercial Snort installations I think it could lead to "information overload" with the number of blocks and unblocks that routinely happen. An improvement might be to filter the events and only send notifications for high priority ones so that you don't get an e-mail flood for something like blocks/unblocks from IPs on the RBN or CIARMY lists.
Bill
-
I agree. Currently it would mean that I would get about 1000+ emails a day and I dont have time for that…
It would consume a LOT of space on the mailserver for nothing really.
-
Guys I updated and lost all my settings - no big deal but now I have an issue with http_inspect.
Constantly sites like google, reddit, imgur, yahoo, youtube…the list goes on... are getting blocked.
Can you please tell me what I am doing wrong with the setup of this and if any of you are seeing the same issues?
I tried to disable it via options but then snort won't start - guessing some WAN categories are dependent on http_inspect starting.
There is a check box on the Preprocessors tab at the bottom of the HTTP_INSPECT section that says "disable http_inspect alerts" or something similar. Tick that box. You should then no longer get blocks from HTTP_INSPECT alerts. There is also a new button at the bottom of the page for 2.5.8 that will reset all the preprocessor settings to their defaults. The default for HTTP_INSPECT should be enabled but with alerts disabled.
Attached below are my HTTP_INSPECT settings. You can also automatically add problem alerts to the Suppress List by clicking the plus icons (+) under the alert on the Alerts tab. Once you do this, you will need to stop and restart Snort to pick up the change.
Bill
Thanks for that…but I am still getting alerts and blocks for it?
Have changed my settings to be exactly the same as yours and still getting things like this:
-
Guys I updated and lost all my settings - no big deal but now I have an issue with http_inspect.
Constantly sites like google, reddit, imgur, yahoo, youtube…the list goes on... are getting blocked.
Can you please tell me what I am doing wrong with the setup of this and if any of you are seeing the same issues?
I tried to disable it via options but then snort won't start - guessing some WAN categories are dependent on http_inspect starting.
There is a check box on the Preprocessors tab at the bottom of the HTTP_INSPECT section that says "disable http_inspect alerts" or something similar. Tick that box. You should then no longer get blocks from HTTP_INSPECT alerts. There is also a new button at the bottom of the page for 2.5.8 that will reset all the preprocessor settings to their defaults. The default for HTTP_INSPECT should be enabled but with alerts disabled.
Attached below are my HTTP_INSPECT settings. You can also automatically add problem alerts to the Suppress List by clicking the plus icons (+) under the alert on the Alerts tab. Once you do this, you will need to stop and restart Snort to pick up the change.
Bill
Thanks for that…but I am still getting alerts and blocks for it?
Have changed my settings to be exactly the same as yours and still getting things like this:
And you did restart Snort after the change, correct?
If you did, and are still getting the alerts, then click on the (+) icon under the SID column on the Alerts tab. That will add the Generator ID:Signature ID for that alert to the Suppress List. After doing this, stop and restart Snort on the Snort Interfaces tab. That should for sure silence the alert.
If you restarted Snort after changing the Preprocessor settings and still got the alerts, post back and let me know. That should have silenced them, and if it did not, I need to investigate that in the code.
Bill
-
hmmm right some weird stuff happening now.
I restarted snort under the interfaces tab after checking
Turn off alerts from HTTP Inspect preprocessor. This has no effect on HTTP rules. Default is Checked.
But still getting the IPs blocked for http_inspect.
So as you said I tried to add to the suppress list:
However when I go to the suppress list there is nothing entered?
I am going to try to re-install snort right now and see if that helps! -
hmmm right some weird stuff happening now.
I restarted snort under the interfaces tab after checking
Turn off alerts from HTTP Inspect preprocessor. This has no effect on HTTP rules. Default is Checked.
But still getting the IPs blocked for http_inspect.
So as you said I tried to add to the suppress list:
However when I go to the suppress list there is nothing entered?
I am going to try to re-install snort right now and see if that helps!I do believe you will need to manually create it first. Mine working as I already have suppress list
-
okay quick update
uninstalled snort
re-installed it
put all my setting back to how they were.
having the check box ticked for it to not block for http_inspect issues didn't work.
So added that ID to the suppress list as you said - this seems to have worked now.
need any logs from me to see why the http_inspect check box isn't working?
-
okay quick update
uninstalled snort
re-installed it
put all my setting back to how they were.
having the check box ticked for it to not block for http_inspect issues didn't work.
So added that ID to the suppress list as you said - this seems to have worked now.
need any logs from me to see why the http_inspect check box isn't working?
With that box checked, you will see the alerts logged on the Alerts tab, but you should not be getting blocks for those IP addresses on the Blocked tab. If you are no longer getting blocks for those IPs listed on the Blocked tab, then the check box is working correctly. It's a bit of a misnomer with the titling. The Alerts tab is really just reading the Snort logs. Snort will log everything. What pfSense calls blocks on the Blocked tab is what Snort calls alerts. A little confusing, probably for new users. When you put something on the Suppress List, it will no longer cause blocks, but will still get logged on the Alerts tab (since the event will be logged by Snort). If you truly do not want to even see the event in the logs, then you have to disable the rule. Your screenshot was of the Alerts tab, so I assume the Blocked tab no longer shows an active block for those hosts listed.
As to the blank Suppress List page, go to the If Settings tab for the WAN interface and post a screenshot of the Suppression List setting in the drop-down near the bottom of the page. Unless you specifically had a name set there, it should be either "default" or "wansuppress".
Bill
-
yea the box was checked and the hosts were getting blocked
100% sure on this because as soon as the host ip was on that block list the website in question would stop working.
-
Anyone still having issues where a blocked IP is removed from snort2c within a few minutes? I'm banging my head here. I've set it for never expire, disabled log limit and removed the 2 cron jobs. They still disappear. I've done a clean install of snort with my old config.. Only 2 options left are to either wipe all snort settings and start fresh or rebuild my box from iso install..
-
Anyone still having issues where a blocked IP is removed from snort2c within a few minutes? I'm banging my head here. I've set it for never expire, disabled log limit and removed the 2 cron jobs. They still disappear. I've done a clean install of snort with my old config.. Only 2 options left are to either wipe all snort settings and start fresh or rebuild my box from iso install..
When the packet filter is reloaded the table "snort2c" will be cleared. This can have many causes and the log file should give clues. It is discussed before.
-
Anyone still having issues where a blocked IP is removed from snort2c within a few minutes? I'm banging my head here. I've set it for never expire, disabled log limit and removed the 2 cron jobs. They still disappear. I've done a clean install of snort with my old config.. Only 2 options left are to either wipe all snort settings and start fresh or rebuild my box from iso install..
gogol is correct. Anything that causes pfSense to reload the packet filter will automatically dump the table Snort's output plugin uses to implement blocks. Reloads can happen because of edits within the GUI, DHCP address changes, links going up and down, etc. Look for the tag check_reload_status: Syncing firewall in the system log. That's an event that clears the table, I believe.
Not really sure why this is a big deal to folks, though. If an offending packet for that IP traverses the firewall again, the IP will be "re-blocked". Or put another way, if whatever caused it to get blocked in the first place repeats, then it will be blocked again. Maybe I'm missing something?
Bill
-
I've been away for a couple of weeks and when I brought it up last month, there wasnt a reason why. Going thru my cron jobs, there is a job that re-sync every 15 minutes so that would explain why the table is being cleared..
This is new behavior for snort. I've been using snort on pfsense for many years and it never acted this way. And if it did, I've never noticed it while testing for last 2 developers of the snort package. This is why I bring it up.
-
I've been away for a couple of weeks and when I brought it up last month, there wasnt a reason why. Going thru my cron jobs, there is a job that re-sync every 15 minutes so that would explain why the table is being cleared..
This is new behavior for snort. I've been using snort on pfsense for many years and it never acted this way. And if it did, I've never noticed it while testing for last 2 developers of the snort package. This is why I bring it up.
Snort really has nothing at all to do with clearing the snort2c table. Perhaps pfSense made some changes to the expiretable script? All the Snort package does is create a cron task that executes every 5 minutes. That tasks looks for snort2c entries that have had no activity for the last period specified in the "Clear Blocks Interval" on the If Settings tab. Entries matching that are removed. You can see the content of the cron task in /etc/crontab. Here is the line:
*/5 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -t 3600 snort2cI have mine set for 1 hour, hence the 3600 seconds value. The expiretable script is used to clear a number of other tables as well and is not proprietary to Snort. I have not noticed any premature clearing of entries on my system, but Snort is the only package I run. Perhaps something else loaded on your firewall is triggering the reloading of the packet filter and thus dumping the snort2c table?
Bill
-
I figured out what was clearing it. My rules would reload every 15 minutes because of schedule fw rule I have (pfsense creates this cron if you have schedule fw rules). I've had this rule for a while.. Either I haven't noticed it clearing out snort2c or like you said, something change with the expiretable script itself on 2.1. What I dont understand, if you set it for never; a simple reload of the rules will wipe it out. I'll have to dig deeper on why this is because I would think other tables would get wiped out then.
Thank you again for all your work you have done on this package.. Its come a long way
-
I figured out what was clearing it. My rules would reload every 15 minutes because of schedule fw rule I have (pfsense creates this cron if you have schedule fw rules). I've had this rule for a while.. Either I haven't noticed it clearing out snort2c or like you said, something change with the expiretable script itself on 2.1. What I dont understand, if you set it for never; a simple reload of the rules will wipe it out. I'll have to dig deeper on why this is because I would think other tables would get wiped out then.
Thank you again for all your work you have done on this package.. Its come a long way
The key is that it's not Snort that really does the blocking/unblocking of an IP. Not directly, anyway. A third-party plug-in called Spoink is compiled into Snort as an output plugin. This plugin inserts itself into the Alert chain in Snort so that it gets a copy of every alert. It then compares the IP addresses in the alert to the Whitelist, and if there is no match based on the SRC/DST/BOTH logic it uses pfctl to insert the IP into the packet filter engine. At that point any part of Snort is done with the block.
I suspect what happens is the reload of the firewall rules on the scheduled task is wiping the block table. That is logical, because on the assumption a new set of rules are coming into play, you would not want old blocks leftover in the block table. In this scenario, Snort's snort2c table is essentially "collateral damage" as they say… :D
Bill
