Snort Subscriber rule in suricata

bmeeks

@MagikMark said in Snort Subscriber rule in suricata:

Hi bmeeks!

Thanks for the reply here is my disk size. Reverted back to RAM disk as I do not know how to resize things in SSD. I do not use Squid or Squid Guard

I still got same error messgae

The disk size you see before or after a rules update is not relevant. As I mentioned, the update job cleans all its files when it terminates, so any out-of-disk space issue would disappear (because the job deletes the corrupt files and all others it downloaded and expanded).

You would need to view the disk space during the actual period of time the rules update job is executing. Any disk space issues would be logged to the pfSense system log under STATUS > SYSTEM LOGS.

If your Oinkcode was invalid, you would be seeing a different HTTP error code in the update log because your firewall would be denied connection to the resource completely. An invalid MD5 checksum means the downloaded file was corrupt. Number one cause of that is insufficient disk space during the rules update job. Its remotely possible there is an issue with the AWS server farm you are routed to, but that would be really unusual. And if that's the case, you can't do anything about that except wait for the remote end to be repaired.

MagikMark

Thanks a lot bmeeks for the assistance.

Right now I disabled Suricata and installed Snot package. I copied the configuration from Suricata to Snort and surprisingly everything is running smoothly. Rules update are running as expected.

How do I make a clean install of Suricata? I want to delete everything related to it and reconfigure it from scratch

bmeeks

@MagikMark said in Snort Subscriber rule in suricata:

Right now I disabled Suricata and installed Snot package.

Eww!! Installing the Snot package is going to make your firewall look kind of gross . Might want to stock up on tissues.

Just having a little fun with your typo -- suspect you mean the Snort package.

bmeeks

@MagikMark said in Snort Subscriber rule in suricata:

How do I make a clean install of Suricata? I want to delete everything related to it and reconfigure it from scratch

Reinstall the Suricata package, then go to the GLOBAL SETTINGS tab and uncheck the option to retain settings when deinstalling. Save that change.

Next, remove the package again using the SYSTEM > PACKAGE MANAGER menu. During the package removal all the Suricata configuration information will be wiped from the firewall's config.xml file.

The next time you install the package, it will start with an empty configuration.

By the way, what Snort rules filename did you have enabled in Suricata? The download code is pretty much identical in the two packages with the only difference being Snort automatically determines which Snort VRT file version to download by querying the version of the installed Snort binary. Suricata obviously cannot do that, so it depends on the admin specifying the proper filename on the GLOBAL SETTINGS tab. But if you specified an incorrect filename, I would expect some type of HTTP "resource not found" error (like maybe a 404 error), but not a checksum error.

MagikMark

I use this URL:

https://www.snort.org/downloads/subscriber/snortrules-snapshot-29200.tar.gz

Then I use this filename:

snortrules-snapshot-29200.tar.gz

Is it correct?

MagikMark

Hi Bmeeks!

I resintalled Suricata and disabled custom url and removed "Enctytion: Bypass" in the custom setting. Evrything is now working fine. Dunno which one of the two is the culprit.

I have Ryzen 3200G, 16GB of memmory and 256GB of SSD, what other setting I could tweak for maximum performance, so far I have done the ff:

Max Pending Packet : 10240 (only 20% memmory usage)
Detect Engine Profile: High
Signature Group Header MPM Content: Full
Run Mode: Workers
IPS Mode: Inline

I am able to saturate my 700Mbps line without VPN and around 620Mbps with VPN

Are there other settings that will help us maximixe Suricata and pfSense under Systl, Loader conf & Local?

Thanks Again

bmeeks

@MagikMark said in Snort Subscriber rule in suricata:

I use this URL:

https://www.snort.org/downloads/subscriber/snortrules-snapshot-29200.tar.gz

Then I use this filename:

snortrules-snapshot-29200.tar.gz

Is it correct?

Yes, that is the correct filename. But for the Snort rules you should not specify the URL. The package has an internal hard-coded URL for those rules since they are included in the default choices. All you need to provide for the Snort VRT rules is your Oinkcode in the proper location.

You did not say earlier that you had specified a custom URL. What did you put in there? That option is only for including rule sets that are not already listed in the GUI. Plus you have to properly handle the MD5 settings in the Custom URL section.

bmeeks

@MagikMark said in Snort Subscriber rule in suricata:

Are there other settings that will help us maximixe Suricata and pfSense under Systl, Loader conf & Local?

Depending on the specific NIC you have, there may be some useful tweaks in this Sticky Post located near the top of the IDS/IPS sub-forum: https://forum.netgate.com/topic/138613/configuring-pfsense-netmap-for-suricata-inline-ips-mode-on-em-igb-interfaces.

bmeeks

@MagikMark said in Snort Subscriber rule in suricata:

disabled custom url and removed "Enctytion: Bypass" in the custom setting.

It would have been extremely helpful to me if you had shared this setting in your original post. That is most definitely not the way to enable the Snort VRT rules. No wonder you had problems.

I assumed in my suggestions that you were following the standard and accepted method of enabling Snort VRT rules. You simply check the box to enable them and provide your Oinkcode and the Snort VRT filename (without the URL) in the box provided on the GLOBAL SETTINGS tab.

pfsjap

@bmeeks Do you recommend those tweaks in the Sticky Post also for igc?

bmeeks

@pfsjap said in Snort Subscriber rule in suricata:

@bmeeks Do you recommend those tweaks in the Sticky Post also for igc?

I don't know. I did not create that post - another user contributed the information there. Different NICs of course can have different customizable settings. You will need to research the particular flavor of igc chip your NIC has to see what might apply. There are families of NIC controller chips that all can use the same generic FreeBSD driver, and each variant in the family might have its own unique settings that another vendor's igc NIC does not share.