Upgrading from 25.1.12 (system running fine since install ing 25.1 earlier this year) to 25.7
GUI appeared to download all packages and install everything without any errors as far as could tell & system went on to reboot but never came back up.
Hooked up a monitor and rebooted to get the following
(the following is manually typed from a photograph of the screen using mobile phone so there could be some typo's in there but I think it's correct.)
>>> Invoking import script 'importer'
Configuring crash dump device: /dev/ada0p3
swapon: adding /var/ada0p3 as swap device
.ELF ldconfig path /lib /usr/lib /usr/lib/compact /usr/local/lib /usr/localpsec /usr/local/lib/perl5/5.40 mach/core
32-bit compatability ldconfig path:
done.
chown: /var/run/booting: No such file or directory
>>> Invoking early script 'upgrade'
>>> Invoking early script 'configd'
Generating configuration configd socket missing <@var/run/configd.socket>
>>> Error in early script '15-templates'
>>> Invoking early script 'backup'
>>> Invoking backup script 'captiverportal'
>>> Invoking backup script 'dhcplease'
>>> Invoking backup script 'duid'
>>> Invoking backup script 'netflow'
>>> Invoking backup script 'rrd'
>>> Invoking backup script 'carp'
CARP event system: configd socket missing <@var/run/configd.socket>
>>> Error in early script '90-carp'
Launching init sysm...done.
Initalizing................done.
(system hangs at this point. Hitting Ctrl C gives)
Enter full pathname of shell or RETURN for /bin/sh:
root@:/ #
power cycling still gave the same issue.
As a result I have used "bectl activate snapshot_name" to revert to a previous snapshot and everything is running fine.
Can anyone shed any light on what the problem may be please?
Do you have a microcode plugin installed? Some people had similar issues with it (especially with Intel hardware).
Cheers,
Franco
I think I do I have this
"os-cpu-microcode-intel (installed)" listed under plugins is that the one you are referring to. I can't remember why I installed it?
Do you suggest disabling / uninstalling it and trying the update again?
sorry should have said it is intel
"Intel(R) Celeron(R) J4125 CPU @ 2.00GHz (4 cores, 4 threads)"
What is the solution to mitigate this issue?
Shall we uninstall the os-cpu-microcode-intel plugin? I haven't updated yet and my firewall is headless. It's rather complicated to connect it to a monitor and keyboard, thus I'd like to avoid having to do so.
What about after the upgrade? Is it safe to install the os-cpu-microcode-intel plugin again, or will it hang after the next reboot? There must have been a reason why I installed the plugin. I believe it was franco's suggestion to do so at one point.
Since it depends on the hardware and there is no list of "known bad Intel hardware with microcode version xyz" I can make no useful suggestion.
Deinstall microcode, get the latest BIOS flashed (which hopefully has the latest version) and then update.
Cheers,
Franco
Thanks for the reply.
Well, I guess this will be more problematic than I thought. I am using one of these mini PCs (see attachment) and I have no idea how to actually get an update for the BIOS in this thing. I bought it 4 years ago and I've never touched it again since the initial install. I've always just upgraded OPNsense remotely. But hearing that the upgrade might hang made me a bit nervous. I guess I will have to find a way to connect it to a monitor and keyboard after all.
P.S.: miniPC QOTOM Q330G4, i3-4010U CPU, AES-NI, 4 Intel LAN (I211-AT 10/100/1000 GbE)
If it helps anyone, I've successfully upgraded:
A CWWK N100, AliExpress jobber with os-cpu-microcode-intel installed
Numerous R86S N100's with os-cpu-microcode-intel installed
So far, all have upgraded with no issues. (3 done so far, 1 to go)
My Protectli NUC upgraded with no issues - I have os-cpu-microcode-intel installed
Uninstalled the os-cpu-microcode-intel microcode & rebooted to make sure it took effect.
Ran the upgrade to 25.7 device hung, power cycled it and it came up OK so removing the microcode did improve the situation. Unfortunately I'm running this router headless so could not see any errors on screen - I have to take it out of the rack to attach a monitor to it.
I'm going to continue running it without the microcode installed and see how it goes. Following on from Franco said earlier I will look it there is a BIOS update available, it's a small fan less PC so may need to do some research to find it.
PS big thank you to Franco for you extremely rapid and helpful suggestion, I love this community.
Sure thing! :)
I have same issue. Device with CWWK with N-305 with microcode plugin installed. Started 25.7 upgrade and then it hangs. It is headless, so I dont have clue what happened, need to go there and check what is on console. I dont understand why uninstalling microcode could help and if it is just with this upgrade or any other later, or general with boot process itself.
I don't know why but I have had problems with major upgrades from gui. For me this is the first that had no problems. Upgrading to 25.1 I had to do a fresh install and import settings on install. If you continue to have issues that may be the way to go.
My experience:
Qotom Q355G4 ugrade to 25.7 with microcode installed, upgrade hung on reload firwmare.
Reinstalled 25.1, reload backup and other settings/plugins/etc, updated to last version, unistalled microcode plugin, reboot, upgrade to 25.7, reinstalled microcode, reboot.
Upgrade went well,
however i've some problem of packet loss on the gateway of wireguard vpn.
Unistalled microcode plugin, no more "loss" on wireguard vpn gateway.
(post scriptum:
i investigated the anomaly of the lost packages, it was due to vpn server side causes and not the opnsense router)
Thanks @nbca2
This info certainly helps a lot. Thus I'll uninstall the microcode plugin before the upgrade and won't install it afterwards.
P.S.: I don't know how to mention a user in this forum.
Quote from: tessus on July 25, 2025, 09:10:24 AMThanks @nbca2
This info certainly helps a lot. Thus I'll uninstall the microcode plugin before the upgrade and won't install it afterwards.
P.S.: I don't know how to mention a user in this forum.
remember i'm not a tech guy, but a tech enthusiast
i don't understand if microcode is necessary for system security.
I have the concept of the microcode update and why I installed it.
However, I don't know why it conflicts with this version of opnsense and I don't know what it means by uninstalling the plugin (in addition to not have the CPU microcode updated).
Similar situation, hooked up an Monitor and it appeared that the SSD was bad, stating when 25.7 was installed that it needed to recover clusters etc. then eventually would not boot. Uninstalled 25.7 and reinstalled 25.1.12 and no issues 2 days and counting. May try removing the Intel Microcode later and trying to install 25.7 again, spent an entire day troubleshooting. I am running the Glovary Mini PC with N100 Alder Lake CPU
Quote from: vk2him on July 24, 2025, 11:20:27 AMMy 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.
Thanks for your feedback, I dont have microcode plugin installed, but reading this experiences, i will wait till see how this issue progress. I´m also based in intel,snfd I don´t want to restore the installation at all.
I've got a Minisforum UN100D that's based on the N100 Intel processor that is normally headless, and a bit of a chore to hook up to monitor and keyboard, and it has the microcode plugin installed.
Based on this I think I'll wait to upgrade, and I'll monitor here for people's experience.
I appreciate the forum all the more, thank you.
There's a risk that we'll never know what the trigger is or that this "bug" will never be found/fixed (especially if it's a vendor issue).
FWIW, I had success on two Protectli units (a V1410 and a VP2410) both with the intel-microcode package installed prior to upgrade. They both are running coreboot rather than the stock AMI UEFI, in case that makes a difference.
Quote from: JDabbs on July 24, 2025, 11:45:01 AMUninstalled the os-cpu-microcode-intel microcode & rebooted to make sure it took effect.
Ran the upgrade to 25.7 device hung, power cycled it and it came up OK so removing the microcode did improve the situation. Unfortunately I'm running this router headless so could not see any errors on screen - I have to take it out of the rack to attach a monitor to it.
I'm going to continue running it without the microcode installed and see how it goes. Following on from Franco said earlier I will look it there is a BIOS update available, it's a small fan less PC so may need to do some research to find it.
PS big thank you to Franco for you extremely rapid and helpful suggestion, I love this community.
I highly recommend using a PIKVM for this type of situation. I also run my servers headless but still need console from time to time. Works flawlessly.
Finally realized that I did Not have os_cpu_microcode_intel installed on v25.1.12 so I installed and checked for updates, installed v25.7 and it came up clean. Have rebooted three times to make sure and no issues.
When you install the microcode plugin, does it tell you that the code updates are not reliable or not fruitful (or something like that), and that you might want to rethink installing it?
Quote from: BrandyWine on July 27, 2025, 05:29:06 PMWhen you install the microcode plugin, does it tell you that the code updates are not reliable or not fruitful (or something like that), and that you might want to rethink installing it?
It did indeed state that the microcode would no longer be supported nor updated. Decided to try it out anyway since I have had issues updating/clean install v25.7 since it was released.
i tried update the backup router, topton with intel j6413, also with microcode plugin installed, also with ami bios (but different version/type from qotom one on my primary router); upgrade stuck with the same error.
I also tried to contact vendor to upgrade bios, qotom answered, i've upgraded to last firmware, but upgrade still stuck with same error.
i'm consider to remove the plugin and then upgrade to 25.7.
Is there a downside to run opnsense without microcode plugin installed (are there security risk?).
If the plugin wil be deprecated, why bothering about it?
Thanks
Quote from: nbca2 on July 27, 2025, 10:23:33 PMIf the plugin wil be deprecated, why bothering about it?
Who's claiming it is deprecated? Microcode updates are essential, IMHO.
I also fail to see where that is said. The info about os-microcode-intel and/or os-cpu-microcode-amd does not state anything to that extent.
And there are no security risks as long as you can accomplish to update the microcode via BIOS updates. But: Many systems out there may not be elegible for that, either because they are out of warranty (being old repurposed boxes) or their manufacturers do no support that in the first place (many chinese boxes fall into that category).
IDK why some systems with that plugin failed on reboot after the update, FWIW, I did not have that problem on any of may 7 machines.
Quote from: meyergru on July 27, 2025, 10:48:29 PMI also fail to see where that is said. The info about os-microcode-intel and/or os-cpu-microcode-amd does not state anything to that extent.
And there are no security risks as long as you can accomplish to update the microcode via BIOS updates. But: Many systems out there may not be elegible for that, either because they are out of warranty (being old repurposed boxes) or their manufacturers do no support that in the first place (many chinese boxes fall into that category).
IDK why some systems with that plugin failed on reboot after the update, FWIW, I did not have that problem on any of may 7 machines.
During the install of the plug in 'Console Window' when it downloads, extracts and installs there is a message that states about depreciation. Sorry did not think about notating the details.
Here are the details:
Reloading firmware configuration
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:
--
This port includes an RC script, which is one of two methods to update
the CPU microcode on a FreeBSD system.
1. Early loading.
This method does not use the RC script included here.
This is the preferred method, because it ensures that any CPU features
added or removed by a microcode update are visible to the kernel by
applying the update before the kernel performs CPU feature detection.
To enable updates using early loading, add the following lines to
/boot/loader.conf:
cpu_microcode_load="YES"
and the appropriate one of these lines:
cpu_microcode_name="/boot/firmware/intel-ucode.bin"
cpu_microcode_name="/boot/firmware/amd-ucode.bin"
The microcode update will be loaded when the system is rebooted.
AMD systems running FreeBSD prior to 2024-02-22 snapshot
34467bd76 only support late loading.
2. Late loading.
This method, which does use the RC script included here, is enabled by
adding the following line to /etc/rc.conf:
microcode_update_enable="YES"
The microcode update is then applied upon reboot or when the microcode
update service is run via:
# service microcode_update start
If the CPU requires a microcode update, a console message such as the
following will appear:
Updating CPU Microcode...
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl0 from rev 0x17 to rev 0x22... done.
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl2 from rev 0x17 to rev 0x22... done.
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl4 from rev 0x17 to rev 0x22... done.
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl6 from rev 0x17 to rev 0x22... done.
Done.
It is safe to enable both methods.
=====
Message from x86info-1.31.s03_1:
--
===> NOTICE:
This port is deprecated; you may wish to reconsider installing it:
Abandoned upstream, fails to identify anything remotely new according to upstream issue reports.
It is scheduled to be removed on or after 2025-06-30.
=====
Message from cpu-microcode-amd-20241121:
--
Refer to the cpu-microcode-rc installation notes to enable AMD microcode
updates.
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***
And as you can see, the notice pertains only to the x86info package, which installs alongside the microcode update in order to be able to actually query which microcode is loaded, not to the microcode package itself.
Quote from: meyergru on July 27, 2025, 11:27:04 PMHere are the details:
Reloading firmware configuration
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:
--
This port includes an RC script, which is one of two methods to update
the CPU microcode on a FreeBSD system.
1. Early loading.
This method does not use the RC script included here.
This is the preferred method, because it ensures that any CPU features
added or removed by a microcode update are visible to the kernel by
applying the update before the kernel performs CPU feature detection.
To enable updates using early loading, add the following lines to
/boot/loader.conf:
cpu_microcode_load="YES"
and the appropriate one of these lines:
cpu_microcode_name="/boot/firmware/intel-ucode.bin"
cpu_microcode_name="/boot/firmware/amd-ucode.bin"
The microcode update will be loaded when the system is rebooted.
AMD systems running FreeBSD prior to 2024-02-22 snapshot
34467bd76 only support late loading.
2. Late loading.
This method, which does use the RC script included here, is enabled by
adding the following line to /etc/rc.conf:
microcode_update_enable="YES"
The microcode update is then applied upon reboot or when the microcode
update service is run via:
# service microcode_update start
If the CPU requires a microcode update, a console message such as the
following will appear:
Updating CPU Microcode...
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl0 from rev 0x17 to rev 0x22... done.
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl2 from rev 0x17 to rev 0x22... done.
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl4 from rev 0x17 to rev 0x22... done.
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl6 from rev 0x17 to rev 0x22... done.
Done.
It is safe to enable both methods.
=====
Message from x86info-1.31.s03_1:
--
===> NOTICE:
This port is deprecated; you may wish to reconsider installing it:
Abandoned upstream, fails to identify anything remotely new according to upstream issue reports.
It is scheduled to be removed on or after 2025-06-30.
=====
Message from cpu-microcode-amd-20241121:
--
Refer to the cpu-microcode-rc installation notes to enable AMD microcode
updates.
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***
And as you can see, the notice pertains only to the x86info package, which installs alongside the microcode update in order to be able to actually query which microcode is loaded, not to the microcode package itself.
thanks for the clarification, i misread the output
Quote from: Patrick M. Hausen on July 27, 2025, 10:34:33 PMQuote from: nbca2 on July 27, 2025, 10:23:33 PMIf the plugin wil be deprecated, why bothering about it?
Who's claiming it is deprecated? Microcode updates are essential, IMHO.
Right in the plugin info when you install it. Who wrote that plugin?
That info is coming from the x86info package, not from the plugin. See above.
Quote from: turipriv on July 25, 2025, 03:36:28 PMQuote from: vk2him on July 24, 2025, 11:20:27 AMMy 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
I have a Protectli V1410 and also faced this issue
Hi,
I have been running OPNsense on a (Chinese) CWWK micro PC Intel N305 (https://cwwk.net/products/12th-gen-intel-firewall-mini-pc-alder-lake-i3-n305-8-core-n200-n100-fanless-soft-router-proxmox-ddr5-4800mhz-4xi226-v-2-5g?variant=44613920555240) for a about a year with zero issues.
When I upgraded to 25.1.12 (and subsequently also direct to 25.7 from img) my router crashes at a random but fairly short time from successful installation. I have made 3 attempts so far, so before I try again I need to change something.
I wasn't able to get log files but I did manage to submit a couple of crash reports and before reinstalling 25.1 from an image (still runs flawlessly).
CORRECTION : My installation appears to include the plugin : os-cpu-microcode-intel v1.1 when it updates to 25.1.12 but it is not installed in 25.1
Unsure how to proceed, advice appreciated
Quote from: meyergru on July 27, 2025, 11:27:04 PMHere are the details:
Reloading firmware configuration
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:
--
This port includes an RC script, which is one of two methods to update
the CPU microcode on a FreeBSD system.
1. Early loading.
This method does not use the RC script included here.
This is the preferred method, because it ensures that any CPU features
added or removed by a microcode update are visible to the kernel by
applying the update before the kernel performs CPU feature detection.
To enable updates using early loading, add the following lines to
/boot/loader.conf:
cpu_microcode_load="YES"
and the appropriate one of these lines:
cpu_microcode_name="/boot/firmware/intel-ucode.bin"
cpu_microcode_name="/boot/firmware/amd-ucode.bin"
The microcode update will be loaded when the system is rebooted.
AMD systems running FreeBSD prior to 2024-02-22 snapshot
34467bd76 only support late loading.
2. Late loading.
This method, which does use the RC script included here, is enabled by
adding the following line to /etc/rc.conf:
microcode_update_enable="YES"
The microcode update is then applied upon reboot or when the microcode
update service is run via:
# service microcode_update start
If the CPU requires a microcode update, a console message such as the
following will appear:
Updating CPU Microcode...
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl0 from rev 0x17 to rev 0x22... done.
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl2 from rev 0x17 to rev 0x22... done.
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl4 from rev 0x17 to rev 0x22... done.
/usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl6 from rev 0x17 to rev 0x22... done.
Done.
It is safe to enable both methods.
=====
Message from x86info-1.31.s03_1:
--
===> NOTICE:
This port is deprecated; you may wish to reconsider installing it:
Abandoned upstream, fails to identify anything remotely new according to upstream issue reports.
It is scheduled to be removed on or after 2025-06-30.
=====
Message from cpu-microcode-amd-20241121:
--
Refer to the cpu-microcode-rc installation notes to enable AMD microcode
updates.
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***
And as you can see, the notice pertains only to the x86info package, which installs alongside the microcode update in order to be able to actually query which microcode is loaded, not to the microcode package itself.
Appreciate the clarification (still learning) I have loaded the Intel V1.1 of the plug in and still received the message about depreciation but not all the detail that you provided (appears to be an older and x86?)so going forward the microcode as long as it is v1.1 and not x86 will receive updates without special intervention?
Thank you all that replied
Mark
As I am stubborn, I re-upgraded my system to version 25.7 (uninstalling the microcode-intel plugin first).
By reinstalling the microcode-intel plugin at the end of the update (successfully passed), I find the following output in the GUI:
The following 6 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
cpu-microcode-intel: 20250512 [OPNsense]
cpu-microcode-rc: 1.0_2 [OPNsense]
libpci: 3.14.0 [OPNsense]
os-cpu-microcode-intel: 1.1 [OPNsense]
pciids: 20250621 [OPNsense]
x86info: 1.31.s03_1 [OPNsense]
Number of packages to be installed: 6
The process will require 29 MiB more space.
21 MiB to be downloaded.
[1/6] Fetching x86info-1.31.s03_1.pkg: ......... done
[2/6] Fetching pciids-20250621.pkg: .......... done
[3/6] Fetching cpu-microcode-rc-1.0_2.pkg: . done
[4/6] Fetching libpci-3.14.0.pkg: ......... done
[5/6] Fetching cpu-microcode-intel-20250512.pkg: .......... done
[6/6] Fetching os-cpu-microcode-intel-1.1.pkg: . done
Checking integrity... done (0 conflicting)
[1/6] Installing pciids-20250621...
[1/6] Extracting pciids-20250621: ..... done
[2/6] Installing cpu-microcode-rc-1.0_2...
[2/6] Extracting cpu-microcode-rc-1.0_2: .... done
[3/6] Installing libpci-3.14.0...
[3/6] Extracting libpci-3.14.0: .......... done
[4/6] Installing x86info-1.31.s03_1...
[4/6] Extracting x86info-1.31.s03_1: ....... done
[5/6] Installing cpu-microcode-intel-20250512...
[5/6] Extracting cpu-microcode-intel-20250512: .......... done
[6/6] Installing os-cpu-microcode-intel-1.1...
[6/6] Extracting os-cpu-microcode-intel-1.1: .. done
Reloading firmware configuration
*** OPNsense\Kea\KeaDhcpv4 migration failed from 1.0.3 to 1.0.4, check log for details
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:
--
This port includes an RC script, which is one of two methods to update
the CPU microcode on a FreeBSD system.
What does that mean?
*** OPNsense\Kea\KeaDhcpv4 migration failed from 1.0.3 to 1.0.4, check log for details
Why does it show up right after this line:
Reloading firmware configuration
which is the last line of text i can see on video before it crashes, when i try to upgrade from 25.1.12 to 25.7 with microcode plugin installed.
is there a correlation between the two situations or is it just random?
addendum:
i used kea in the past. In KEA DHCPv4 - Reservation was populated with reservation for the router ip. Deleted this line, the installation of the plugin didn't encour the error
......
[4/6] Extracting x86info-1.31.s03_1: ....... done
[5/6] Installing cpu-microcode-intel-20250512...
[5/6] Extracting cpu-microcode-intel-20250512: .......... done
[6/6] Installing os-cpu-microcode-intel-1.1...
[6/6] Extracting os-cpu-microcode-intel-1.1: .. done
Reloading firmware configuration
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:
i tried to delete this line in the backup router and then perform the upgrade from 21.1.12 to 25.7, but it hungs always at Reloading firmware configuration
Quote from: nbca2 on July 25, 2025, 08:30:15 AMUpgrade went well,
however i've some problem of packet loss on the gateway of wireguard vpn.
Unistalled microcode plugin, no more "loss" on wireguard vpn gateway.
i investigated the anomaly of the lost packages, it was due to vpn server side causes and not the opnsense router.
Quote from: vk2him on July 28, 2025, 08:52:05 AMQuote from: turipriv on July 25, 2025, 03:36:28 PMQuote from: vk2him on July 24, 2025, 11:20:27 AMMy 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.
update from 25.7 to 25.7.1, went well, no errors, with intel microcode plugin installed.
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.