Messages

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.

Did you managed to extract the upgrade logs?

I usually take my time when it comes to switching between major releases so I waited for release 25.1.1 before saying goodbye to 24.7.12.

All that being said, both the big jump from 24.7 to 25.1 and the smallest one between 25.1 to 25.1.1 went smoothly.

I have not experienced any issues during the upgrades and so far performances are ace as usual.

For the reference, my current feature set is as follows:

• Unbound DNS with blocklists enabled
• Suricata in IPS mode
• Kea DHCP Server
• NTopNG
• Wireguard ClientVPN

Round of applause to all the team!

Amen to that.

While it is good to jump on the latest major release if you are running it in a test environment, it is definitely worth waiting if your firewall is running in something close to a production environment (whether it is your home network or your company network).

In my case, I'd rather fight with my enthusiasm and wait for the new features to be stable, always thankful to thee community for their hard work.

Upgrade from 24.1.10 to 24.7_9 went smoothly with no issues whatsoever.

After almost one week of usage, I have not experienced a single feature break except for some minor issues with the dashboard widgets that have been solved with today's update to 24.7.1.

My current installation includes:

• ISC DHCPv4 (will move to KEA by the end of the month)
• Suricata in IPS mode
• ntopng
• Wireguard client VPN

Thumbs up to everyone for the great job!

Hi,

I think that what you are looking for in OPNsense is Outbound NAT which normally is configured automatically.



What would happen in this case is that OPNSense automatically translates all your inside IP addresses into its WAN IP address, the IP address of the interface connected to your router.

Your router will then perform another NAT, and translate its inside IP address to its public (outside) address.

If for whatever reason you want to perform 1:1 NAT Manually, you should set outbound nat to either Hybrid or Manual.

More info can be found here: https://docs.opnsense.org/manual/nat.html