Messages

I setup and  Save. error installing ids rules.

Mines spiking to 75% and rendering the whole thing useless but after a random amount of time, it will work fine anywhere from 30 mins to 6 hours then hit 75% and chug along for a while and pass some packets but eventually everything just stops working. Tried updating which turned into an endeavour, ended up having to wipe my disk completely and to a fresh install then upgrade from within console then log out and log back in as installer to get 25.7.1_1 but still having the same freeze issue albeit a lot less often. I'm running in proxmox beta on a hp dl360 g8 and dl380 g9, both had the same issue so I don't think it's hardware related.

This is a sad event. Some big hardware brands have their own ideas.

I have successfully upgraded and it has been running stably for 2 days.

OPNsense 25.7.1_1-amd64 

I have successfully upgraded and it has been running stably for 2 days. Let me update the information. Everything is stable now. If you want to upgrade, you can give it a try.

I've revisited a previous issue: in intrusion detection, users can specify a specific IP address range to block, but the result is a warning, not a block. This allows attackers scanning for the IP address range to access it and carry out their malicious activities. I wonder how many more times this problem will recur.

You made the right choice. And I would wait until the second or third minor version before upgrading. And wait for at least 3 days in the forum to see if there are any major problems before upgrading. Safety first, brother.

wait 25.7.2  25.7.3 

I agree with this idea. If users have different requirements for memory or hard disk, the official can provide a hardware option. Of course, there will be price differences.
Installing an 8GB memory stick and a 32GB memory stick will not have any special technical difficulty or cost.
The CPU and network card fixed on the motherboard can already distinguish users of different series.

After upgrading to the latest version
OPNsense 25.1.9-amd64
FreeBSD 14.2-RELEASE-p3
OpenSSL 3.0.16
In the intrusion detection, the user's customization of the IP address has automatically changed from blocking to warning. The continuous attack I set to block and the scanning of my IP address are all unimpeded.
My God, this problem has happened before, I don't know how many times it will happen.

---------------

The official version can be reproduced as follows:
Copy a rule a in a user-defined rule, and then modify the IP address to be blocked into another rule a. After saving and taking effect, check whether these two rules a and b have changed from the original blocking to warning.

thanks...

The last firmware upgrade (25.1.6_4) fixed it for me.

The last firmware upgrade (25.1.6_4) fixed it for me.

The latest patch on Friday also did not solve the problem.

OPNsense 25.1.6_2-amd64
FreeBSD 14.2-RELEASE-p3
OpenSSL 3.0.16

I just applied the latest patch, but the problem is still not solved:

OPNsense 25.1.6_2-amd64
FreeBSD 14.2-RELEASE-p3
OpenSSL 3.0.16

I wonder if yours has recovered to normal? Or are you still having the same problem as me?

Had the same problem and found this issue/fix. https://github.com/opnsense/core/issues/8550
I applied the patch and I can now read the topmost alert, but nothing else. And there's an open issue describing that bug here: https://github.com/opnsense/core/issues/8569
So looks like they are working on it.

I'm glad to get your reply. It seems that I am still in a long wait.

Versions
OPNsense 25.1.5_5-amd64
FreeBSD 14.2-RELEASE-p2
OpenSSL 3.0.16

Services => Intrusion Detection => administration => Alerts

It is blank and the specific content cannot be viewed.

I woke up to see if there is an update I am looking forward to, 25.1.2... I am really lucky, there is a notification that it is coming.
After reading all the update prompts and making backups, I have to say goodbye to 24.7 (I will miss you), and bravely click the update button. The first step is to update to 25.1, and then to 25.1.2. The process is very smooth, and there are no problems on 3 machines, a Dell, a PVE VM, and a small host the size of a palm.
The login interface has also been updated. After entering the system, there will be a prompt at the top. If a crash is found, send feedback on the crash information, which can be regarded as providing a little insignificant help. After restarting again, the error prompt disappears.
It has been running normally for 2 hours, and everything is normal.
Thanks to the hard work of the developers. Since the launch of 25.1, it can be seen that there are still many feedbacks on problems. The pressure must be great.
I wish you all a happy weekend.