@bmeeks this is working great and I can see now where the vulnerable client is.  Thank you.

I honestly don't think the Snort package is at issue here.  If it was, then I would expect many complaints here of similar nature.  My personal experience is that you do generally want to avoid the period around midnight U.S. Eastern Time.  I would frequently encounter errors then on the nightly downloads.  I moved the update time to 0130 Eastern and no more issues.  I suspected the VRT folks had some kind of server maintenance task running at midnight, but that was just a guess. Since you have problems even with manual downloads, I would look at other basic connectivity problems somewhere.  Is there anything else in the chain like a proxy (Squid perhaps?), another upstream firewall, etc.? Bill

Thanks man! Greatly appreciated!

@MilesDeep: Thanks.  That's easy enough.  Will all the conf files remain intact? Yes, Snort and Suricata upgrades use the existing configuration stored in the config.xml file on the firewall.  The actual snort.conf (or suricata.yaml) conf file for the binary is regenerated each time the binary is started. Bill

@fsansfil: With everything going HTTPS these days a Bluecoat or squid with i-cap and sslbump is better for web filtering than an IPS. You might be better suited with a proxy. "So i am NOT complaining!" No harm, no offense; Its just me after working 12hrs in a row, doing suricata rules ;) F. I have the i-cap/clam anti-virus enabled in my squid3 config

2.1.5 is dead. Move on. No fixes will ever appear there.

As noted above - try without sync. (Hopefully gone everywhere again with 2.2.4.)

Disable the broken rule. And while at it, disable 1:2015526, same idiocy.

Using the ADVANCED PASS-THROUGH option would be the mechanism for using that config directive.  You will find that on the INTERFACE SETTINGS tab for the specific interface. Bill

Swapping cables would be one thing to try.  It is possible that the libpcap library and the USB NIC don't play well together. Bill

Well, the way to mass-disable rules is called SIG Mgmt.

Someone's pinging you… Some rules categories are just horrible idea to enable; icmp_info definitely among them.

Okey dokey, thanks for the clarification :)

If your still having this problem edit your snort interface and check under your "WAN preprocs" that you don't have Application ID Detection enabled. Mine seems to have been enabled with the last update and just realised now.

pfSense 2.1.* is no longer supported so you are running a really old version of Snort. Upgrade your pfSense and try again with the latest version of the package.

If you want to see internal LAN IPs before NAT, you need to run on LAN as well.

Hmmm, WTF… There's something badly rotten with UFS.

@doktornotor: Excellents, thanks! Going to do the same for suricata as well? Yeah, I will port the same fixes/features in Snort over to Suricata.  The Suricata GUI code was cloned from Snort's anyway, so they share a ton of functions with identical code. Bill