Messages

Well, in my experience, I have always upgraded between major releases directly via GUI, and it always went smoothly.

Given the arrival of the new rule interfaces, I was thinking about a clean install for 26.1, but being a couch potato (and not wanting to climb up to the rack cabinet to take the firewall out), I proceeded with a direct upgrade as usual.

It went fine, as usual.

All that being said, everything depends on your specific needs.

Sooner or later, I will perform a clean install, mostly because I want to switch from UFS to ZFS; apart from that, I would probably go with a direct upgrade all the time.

Just upgraded to 26.1 and it went smoothly as always.

After upgrading, I removed some stale configurations of old plug-ins and uninstalled the legacy ISC plug-in, as I had switched to Kea a few releases ago.

For the foreseeable future, I plan to migrate to the new rule interface, as I'm pretty eager to test the Divert IPS mode, given the potential beneficial impact it may have on overall system performance.

All that being said, I know I say this every time I perform an upgrade, but I really want to congratulate the team for this upteenth smooth experience. I deal with firewalls for a living, and such smooth transitions between major releases are never to be taken for granted.

Your level of dedication and the quality of your work are simply insane!

Did you take a look at this topic?

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

Hi there,

What issue are you facing in enabling it?

Also, do you plan to monitor the WAN-side or the LAN-side?

I just got this rather scary message during the update to 25.7.6. The update appeared to stop.

I couldn't log in at the console, I got this error:

Password:
sh: /usr/local/libexec/opnsense-auth: not found
Login incorrect

The GUI then gave a 404 error.

After a couple of minutes it sprang back into life.

I've never seen this behaviour before - is it expected?

The update appears to have now completed successfully, as far as I can tell.

I had the same "Danger. Unexpected error, check log for details" error but when I refreshed the OPNsense main dashboard page, version updated to 25.7.6 and a check for updates came back with "There are no updates available on the selected mirror".

I am reluctant to reboot in case I'm left with a broken OPNsense.

Is there anything I can check to ensure a reboot will succeed?

Same here. I received the error message, but after refreshing, everything is running fine.

Have not rebooted yet, due to the same concern.

Upgrade to release 25.7.6 went pretty smoothly except for the already announced hiccup related to the package manager upgrade.

The system appears to be stable, especially Suricata running in IPS mode and behaving just fine.

HW and Feature set are as per the signature.

Thanks to the developers for yet another great release.

Finally upgraded.

From 25.1.12 to 25.7, then from 25.7 to 25.7.1_1.

All went smoothly, no error, no crash, no kernel panic.

FWIW, I had the cpu-microcode plugin already installed before performing the upgrades.

My HW is stated in my signature.

Round of applause to the developers for the usually excellent job.

My Protectli NUC upgraded with no issues - I have os-cpu-microcode-intel installed

What model do you have? I have a VP2420 and plan to upgrade during the weekend.

Sorry for delay in reply - I have a VP2410, so the older version of the one you have

Thank you for replying.

I still have to try the upgrade, as my last weekend was a mess.

Hopefully, I will try over the next one.

My Protectli NUC upgraded with no issues - I have os-cpu-microcode-intel installed

What model do you have? I have a VP2420 and plan to upgrade during the weekend.

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


Versions
OPNsense 25.1.6_4-amd64
FreeBSD 14.2-RELEASE-p3
OpenSSL 3.0.16

Hi,

I'm having this same issue. Whenever I click on the "View Alert Info" button, I get an empty pop-up instead of the usual window displaying alert info and allowing me to change the rule disposition.

Tried different browsers and clearing cache as well, to no success.

More of an annoyance than an issue, but a suggestion on how to solve it would be much appreciated.

Same here.

Upgraded without any issue whatsoever.

Excellent job everyone.

Mine wasn't so good. After the update it refuses to connect to the router, basically a local LAN box now. All internal reporting thinks everything is great except it refuses to resolve any DNS to direct IP access.

My only fix might be what I did last time a factory reset!!

That's weird.

What is your topology and DNS configuration?

You said in the past you had to factory reset, were you experiencing the same issue?

If you share some more details we may try to troubleshoot it further.

[Blood, death, and vengeance!]

Hear, hear.  I upgraded and resolved a ip queue issue I was having. 

Code Select Expand

sysctl net.inet.ip.intr_queue_drops
Not sure if the new kernel did it, but everything is working smooth on my end.  Adguard and Unifi controller all hosted bare metal too. 

Good job team!

Blood, death, and vengeance!

I'm sorry, given your nickname I just couldn't help it... :P

So I've never had this issue before, and google isn't helping much. Where in the GUI would I find the upgrade log? Would rather not have to dive into the terminal for this just yet, but I can if no other alternative.

In the firmware upgrade page in the GUI, a Tab is displaying live messages during the upgrade and audits.

Posting its content would be a good start.