Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - KeithRBrown

#1
25.7, 25.10 Series / Re: 25.7.8 upgrade
December 06, 2025, 05:56:30 PM
I'm also getting the "Danger" message.

The first time I saw it, it was during an upgrade from 25.7.7_4 to 25.7.8. Although the update completed, something had clearly gone wrong as nothing was stable after it rebooted (NOTE: you can't stop it from rebooting. The upgrade continues to complete, and then promptly reboots).

I decided to reinstall from the Installation Media (v25.7) and restore my config from backup. This all worked fine, and once I was happy it was stable, I proceeded to progress with the update (this time to 25.7.9, as it had been released by then).

Once again, during the update from 25.7 to 25.7.9, I again got the "Danger" message, and like before the update completed and rebooted. This time though, everything seems stable, so I've just left it in-situ.

Happy to provide logs if it can help determine the root cause.
#2
Uninstalling the microcode plugin also worked for me.

Any idea why booting in verbose mode works though? Seems a bit odd.

Is it best to leave the microcode plugin uninstalled for the moment?
#3
Hi Kewin,

I saw your post, which is why I tried kernel.old, but that didn't work for me. Although our issues do seem similar.

My hardware is an old PC, running an i5-8600K, booting from a SSD (formatted ZFS I believe), and a dual intel 10G NIC. I've been using this for over a year now, without any issues.
#4
Hi,

After upgrading from 25.1.7_4 to 25.1.8_1, OPNsense fails to boot.

The boot sequence hangs indefinitely after it displays "masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000".

However, if I go into boot options, and turn on verbose logging, it boots without any issue.

I also tried switching to kernel.old, but the boot sequence still hangs at the same point.

Thanks,

Keith
#5
A feature which I currently use on ISC DHCPv4 is the ability to override the DNS Server setting in a Static Mapping.

Will this feature be added to KEA DHCPv4 in the future?