Wireguard service not starting at backup SG-3100

FSC830

Hi,
I am using a SG-3100 appliance and setup Wireguard some days ago to use my mobile devices as road warriors, everything runs fine.

In the last days I updated Wireguard to latest version 0.1.6_1, afterwards I did installing Wireguard also at my backup appliance. (Yes, I have got a cold-backup appliance, no HA setting, just for replacing the physical router).
So now I am running with my backup device and all is fine - except Wireguard!

The Wireguard service cant start, for what reasons ever.
After a couple of seconds the service terminates.
In system log I can found this entry:

Feb 18 18:17:51 	kernel 		KLD if_wg.ko: depends on kernel - not available or version mismatch

As fas as I can see, both appliances are identical and showing

12.2-STABLE FreeBSD 12.2-STABLE plus-RELENG_21_05_2-n202579-3b8ea9b365a pfSense-SG-3100  arm

No idea about that, setting up the "primary" appliance in an isolated network (IP settings are identical, I see that WG service is running at this appliance).
But at now active appliance the service denies to start.

Any ideas why Wireguard is not running at this device?

In addition, since some days the Wireguard package is not any longer available for download, was it withdrawn for any reason?

Regards

FSC830

@fsc830

Again I answer myself. Comparing the if_wg.ko at both appliances show that at the "primary" device the .ko is from Nov. 9th 2021 whereas the .ko at backup device is dated from Jan. 13th 2022.
Just replacing this fie and the service keeps running...

Regards

NOCling

Version 0.1.6_1 is for 22.01, you running a Package Update with an old release after an new one is out.
You are a lucky one, another Package could kill the entire system!

If you activate a System with a previous Release, you have to set the Branch first, then look for Package Updates.

Or you go for the new 22.01 Release which addresses some Problems of the 21.05.x Releases.
Like the “pcscd PC/SC Smart Card Daemon Memory Leak”.
If you don’t use a VPN Tunnel for all WAN Traffic, the update is worry free.

FSC830

Yes, thanks, yesterday I noticed that the backup appliance has the wrong branch setting.
Anyhow later this weekend I am going to update to 22.01.
But in advance I switched the appliances to have a quick fallback if something will go wrong.
In that case I change the appliances again, run with 21.05.2 and have all time to install the "standby box" from scratch.

Regards

FSC830

Just to end this: appliance B was updated smooth and successfully from 21.05.2 to 22.01.
All services running.

Regards