If you go into categories, select one and click on the icon top right, what happens? I think it should work  :P

What probably happened is that when we updated the time zone data, your old named zone was moved/renamed/deleted and it defaulted since it didn't know what else to do. We don't make those edits ourselves, however. We get that data from FreeBSD so it must have changed upstream somewhere.

On WAN? Yes, that's not a problem. That's correct. As said, you need to get this working on LAN to see LAN IPs. Explained above, plus explained here by Snort/Suricate maintainer. Really don't think there's much else to add here. P.S. Getting rid of double-NAT is a good thing regardless of IDS alerts.

A couple of issues can cause this.  One is Snort did not get restarted when the last change was made to the suppress list.  This should have automatically happened, but perhaps did not.  A second more rare possibility is that you have a duplicate zombie Snort process running and that process is blocking/alerting. You should have exactly one Snort process per interface where Snort is enabled.  Check that with this command from the CLI: ps -ax |grep snort If you see extra Snort processes, stop Snort then kill any remaining zombie processes and then restart Snort. Bill

There should be sync messages written to the system logs (especially on the destination machine). I probably forgot to add a "sync trigger" to the new OpenAppID code. I will check that so that when it is enabled/disabled, a sync is forced. Bill

@simby: Bill can you please share your list or. PM? Please,.. Here is what I have on my home firewall.  I have not added or removed entries in quite some time… #"(http_inspect) JAVASCRIPT WHITESPACES EXCEEDS MAX ALLOWED" suppress gen_id 120, sig_id 10 #"(http_inspect) HTTP RESPONSE HAS UTF CHARSET WHICH FAILED TO NORMALIZE" suppress gen_id 120, sig_id 4 #"(http_inspect) NON-RFC DEFINED CHAR" suppress gen_id 119, sig_id 14 #(http_inspect) IIS UNICODE CODEPOINT ENCODING suppress gen_id 119, sig_id 7 #"BROWSER-IE Microsoft Internet Explorer userdata behavior memory corruption attempt" suppress gen_id 1, sig_id 16482 #"ET TROJAN Suspicious Malformed Double Accept Header" suppress gen_id 1, sig_id 2008975 #"GPL WEB_CLIENT PNG large colour depth download attempt" suppress gen_id 1, sig_id 2103134 #"FILE-IDENTIFY download of executable content" suppress gen_id 1, sig_id 11192 #"FILE-IDENTIFY Portable Executable binary file magic detected" suppress gen_id 1, sig_id 15306 #ET SCAN Behavioral Unusually fast Terminal Server Traffic, Potential Scan or Infection suppress gen_id 1, sig_id 2013479 #ET SCAN Behavioral Unusually fast Terminal Server Traffic, Potential Scan or Infection suppress gen_id 1, sig_id 2013479 #ET INFO Packed Executable Download suppress gen_id 1, sig_id 2014819 #(smtp) Attempted response buffer overflow: 1448 chars suppress gen_id 124, sig_id 3 #(http_inspect) UNESCAPED SPACE IN HTTP URI suppress gen_id 119, sig_id 33 #(http_inspect) TOO MANY PIPELINED REQUESTS suppress gen_id 119, sig_id 34

@somosane: Jim Thompson speaks about QI integration on his blog entry on https://blog.pfsense.org/?p=1724 Will the pfSense Snort packages have QI detection before upstream integration? Not sure how to interpret the blog post. I won't try to speak for Jim, but my guess is the answer to your question depends on whether or not QI detection is merged into the FreeBSD port of Snort before it makes it into upstream.  If or when that might happen, I have no idea.  I do know that pfSense likes to stay in sync to the maximum extent possible with FreeBSD ports. Bill

Thanks :)

Thanks everyone for their inputs, especially bmeeks . I recently purchase the gold subscriptions :) ,  time for me to do some reading before asking some noob questions. Cheers

Hello Bill, that would be nice ;) many thanks for your dedication.

Thanks doktornotor for the bug report.  It does appear I have some more work to do there with validation of aliases. Bill

Thanks fsansfil, yes i think youre right. All alerts came together and was shown as one. I will have a look at this and try to download again.

Great thanks! I just get nervous when upgrading SNORT as once there was a bug that would clear my block list when it wanted to no matter which option I choose for keeping the list.

Replied to you PM on this topic. Bill

I do recall seeing on the Barnyard2 Github page that OpenAppID events are not supported by Barnyard. Your new error seems to be related to the general issues the newer Barnyard2 code seems to have with SQL.  I became so frustrated with Barnyard2 and Snorby on my own home firewall installation that I just disabled Barnyard2 last month.  Got tired of restarting it and clearing the signature reference table and all the other hassles. Bill

Go to the RULES tab in Snort.  In the Category drop-down, select Custom Rules.  That will open a text window where you can type in your rule.  Click SAVE and you're done… ;). Bill

@Beerman: Had some troubles to update the package. Output of the installation process stops sometimes at "…waiting for snort to start...". Sometimes it stops at "... generating interface configuation...". Even the attempt to remove the package, was sometimes not successful. Output stops at some point. Second try, works... I tried several times the installation, but no success... Snort was running, but no entry in the web-config. Then I restarted "php-fpm", and use the IE (before I was using Firefox - v.38.0.5) and installation was OK and did not take long... I don´t know what helped... My guess is the change of browser, because on console I saw the whole installation process and snort did run after that, but the output stuck. Unfortunately I tried both together... :-( I checked again, today. Removing and installation fails with Firefox 38.0.5 Output at removing of the package stops at: Starting package deletion for snort-2.9.7.3-amd64... Output at installation of the package stops at: Please wait while Snort is started... But with IE11 removing and installing of the package worked. Installation took ~ 5 min.

All rules are logged exactly the same way in the same places (ALERTS tab and also the system log if you have that option enabled).  If you don't have alerts from your Snort VRT Community rules, then either none of the those rules have yet been triggered, or you don't have them actually enabled.  The Community set ships with the vast majority of the rules disabled.  You must enable the ones you want to use.  You do this on the RULES tab by selecting the Community rules in the CATEGORY drop-down and then enabling the rules you want to use. The IPS Policy rules do not false positive very often, so it is normal for them to be quiet. Bill

@SixXxShooTeR: increasing the stream memory cap from 32MB to 64MB fixed the issue. Yes, the old default stream memory setting is too small as of the 2.0.7 release of Suricata.  I will update the default size and make it some larger in the next package update. Bill