Messages

One last test with another configuration. It still does not work. The rule shown in the image as DROP is manually activated.

More screens

I just tried another test with a different configuration and it still doesn't work.

Yes. If I activate the lock setting in the Policy tab according to the following screenshot it does not work.

Nothing works. In the Rulesets section which states that if nothing is selected it applies to everything does not work. And if you select everything it doesn't work either. There is no way to select the rules in blocking. It worked so well before blocking the categories of rules in the Download section, why do you change it?

Clean install Opnsense. Rules: ET Telemetry

Opnsense 21.1

Suricata is one of the best things Opnsense has and in my case it has always worked well. What you have to do is to have it configured correctly. In my case I have it acting in the wan and I can't be happier. The new version of Suricata seems to bring great changes adding better detection protocols and I hope they will integrate it in the new version of Opnsense. And if I have to compare pfsense ( mostly outdated ) - Snort ( gave me a lot of system blocking problems ) with Opnsense + Suricata the choice is safe: Opnsense

The notes of the new version of Opnsense do not say anything about the new version of Suricata. Is the update to Suricata 6.0.1 planned? Many thanks to the developers.

Hello, thanks for the information. I explain. Sensei I had it installed earlier and uninstalled it. I have done the following to make it work. I have uninstalled Sensei. Then I accessed via SSH and looked for the folders you mention.

System: OPNsense 20.7.7_1-amd64

/usr/local/sense-db: Does not exist
/usr/local/datastore: Does not exist

If the following folders exist:

/usr/local/dbsensei
/usr/local/sensei

I have deleted those folders, restarted Opnsense, and reinstalled Sensei. Once Opnsense is restarted, when entering its configuration to start it, it gives me a mongodb error again. I have solved it by entering Opnsense through the console, uninstalling mongodb and re-urging it with these commands:

pkg remove mongodb40
pkg install mongodb40

Once this is done I have restarted Opnsense and when I reconfigured Sensei it has no longer given me a mongodb error and it works correctly. The funny thing is that both when reinstalling mongodb and when configuring Sensei (reinstall mongodb again) the following message appears:

This port is deprecated
It is scheduled to be removed on or after 2020-12-31        ( Attach screenshots )

Is there a future problem with this?

I have managed to install it but when starting the configuration it gives an error.

New Sensei 1.6.2:  https://www.sunnyvalley.io/post/sensei-1-6-2-for-opnsense-is-out/

Install Opnsense missing

New DNS Security Protocol from Cloudflare

Info:    https://blog.cloudflare.com/oblivious-dns/

Updated configuration.

https://forum.opnsense.org/index.php?topic=13445.0