@jbhowlesr:

Would you mind if I hit you up on a side bar private message? I have a few questions about some of the setting in Snort. Basically, I want to understand a little better what they are for and what they mean.

I replied to your PM.

Bill

I finally got it working  ;D ;D ;D

As I have read in another posting, someone succeeded in deactivating all rules, started suricata, then activated the rules and restarted suricata again. Up from that point, suricata started showing alerts at least.

Afterwards I let suricata rebuild the "Interface SID Management File Assignments", that´s when suricata started blocking packages and showing them red in the alerts view.

So maybe there had been some incompatible rules or settings in the older pfs-version-data I imported in 2.3.

Everything seems to be fine now.

Thanks for your help.

You rock Bill. Thank you!

@bmeeks:

The fix for this is waiting for the pfSense developers to approve and merge.  I posted it late last Friday afternoon, so they are probably taking a bit of well-deserved downtime over the weekend.  I expect them to merge the fix this week.

Bill

No problem. I did spend some time looking to see if this was already mentioned. I guess I overlooked it. Thank you however for this fix and all the work you do for Surricata on pfSense.

I already change to AC-BNFA still having the IP to Block source problem, the only way is to use both or destination. many thanks for the help

This will be fixed in the next Snort update, which should be out soon.  Just finished fixing a list of Suricata issues, so now my slate is clean and ready for me to tackle the reported Snort bugs.

Sorry for all the little issues, but the conversion to Bootstrap for pfSense 2.3 was a big chore and lots of little errors crept in.

Bill

Darn it!  I thought I had the Stream Memory Cap default set large enough, but apparently not true in all situations.

Bill

@Creep89:

I experience the same problem on my upgraded 2.3 (2.2.6 -> 2.3). Snort blocks all the IPs, but only one IP is shown under the Blocked tab. But if you download the blocked IP list, you can actually see that far more IPs are blocked.

edit: Nevermind, setting a new value of blocked entries to view and hitting "save" actually resolves the issue, now all blocked IPs are shown.

Ah-ha!  Thanks for posting the solution.  This is an artifact of some Bootstrap fixes.  That value is not being initialized properly.  I will take care of it in the next Snort package update.  I am working on Suricata now, but hope to finish it up today.

Bill

Google doesn't trust their own internal networks so why should anybody else?

It is normal that Google is 24/7 online and a good basis for the scripts called bots (robots) and
from there scans will be a long not able to get rid of them. So many "peoples" are placing then
there bots into Google or other 24/7 sites. If you will be scanned ones more it is not unusual
so if nothing is opened at the WAN interface you can be forget that scans.

@bmeeks:

@Soonie:

You have two running, and one of them is probably a sort of "zombie".  Kill them all and then restart Snort.  This happens now and then for some unknown reason.  Multiple instances get started on the same interface.  I have never been able to pin down the cause.

The two lines showing /usr/local/bin/snort -R 45659 are the duplicate instances on the same interface.

Bill

Oke ThX very much i kill the zombie ;-)

You can use the features on the SID MGMT tab to help automate "turning on" many of the GPLv2 rules.  Go to that tab, enable SID MGMT, then read through the comments in the sample enablesid.conf file.  Click the edit icon beside the file to open it for viewing.  It has comments to show you how to use the feature.  Should you decide to use the feature, create your own enableside.conf file and name it something besides "sample".  That's because those sample files are overwritten on each package reinstall, so if you make changes to the sample files they will get lost on the next update.

Bill

Hi, that works.
Thanks.

Thanks

Thanks Bill.  No NAT in the switch.  I will take another look after my 2.3 upgrade.

Snort and Suricata are way too memory hungry to run on a system with only 256 MB RAM and no swap.

It will vary by location (LAN vs WAN) of the IDS sensor.  Snort and Suricata both see packets from the WAN before they hit the packet filter, so no port translation has yet taken place on inbound (from Internet to your firewall) traffic.  When on the LAN, the IDS is seeing stuff after NAT translation to local addresses/ports.

So think of a series circuit on the WAN side.  You have your NIC, then the IDS, and then the firewall.  So the IDS sees traffic before the firewall does and thus no firewall rules have been evaulated (to say block stuff) and NAT has not yet happened.  This is why the IDS will still alert even for inbound traffic the firewall will later block due to a rule.

Now to get even more technical, Snort (and Suricata when running in the legacy mode) actually use libpcap to get a copy of the packets coming through the circuit from NIC to packet filter.  The IDS operates on this copy while the actual original packet continues through.  If the IDS decides the traffic is malicious, it inserts the offending IP address into the packet filter (firewall) and then kills any states that may have been established when that original packet went on through while the IDS was evaluating the copy.

Bill