26.1.2 - crashed and rebooted

Started by TimmiORG, February 16, 2026, 12:14:54 PM

Previous topic - Next topic
Hi all,

I have updated our OPNsense to 26.1.2 yesterday.
Today it went into a crash and a automatic reboot.

I would like to share the crash report but there are some sensitive information inside that dump.
So would like to understand who will have access to the information which are shared via the report function.

In any case I would like to understand why the crash / reboot happened.

db:0:kdb.enter.default>  bt
Tracing pid 0 tid 100229 td 0xfffff800020e8740
kdb_enter() at kdb_enter+0x33/frame 0xfffffe0035f40e00
panic() at panic+0x43/frame 0xfffffe0035f40e60
dblfault_handler() at dblfault_handler+0x1ce/frame 0xfffffe0035f40f20
Xdblfault() at Xdblfault+0xd7/frame 0xfffffe0035f40f20
--- trap 0x17, rip = 0xffffffff80fbaaa9, rsp = 0xfffffe0106df0fd0, rbp = 0xfffffe0106df10a0 ---
AES_GCM_decrypt() at AES_GCM_decrypt+0x1959/frame 0xfffffe0106df10a0
aesni_cipher_crypt() at aesni_cipher_crypt+0x30f/frame 0xfffffe0106df1170
aesni_process() at aesni_process+0xc6/frame 0xfffffe0106df11a0
crypto_dispatch_one() at crypto_dispatch_one+0xde/frame 0xfffffe0106df11c0
ovpn_udp_input() at ovpn_udp_input+0x492/frame 0xfffffe0106df1270
udp_append() at udp_append+0x67/frame 0xfffffe0106df12f0
udp_input() at udp_input+0x8bb/frame 0xfffffe0106df13e0
ip_input() at ip_input+0x26f/frame 0xfffffe0106df1440
netisr_dispatch_src() at netisr_dispatch_src+0x9f/frame 0xfffffe0106df1490
ovpn_finish_rx() at ovpn_finish_rx+0x405/frame 0xfffffe0106df14e0
ovpn_decrypt_rx_cb() at ovpn_decrypt_rx_cb+0x1a1/frame 0xfffffe0106df1590
aesni_process() at aesni_process+0xea/frame 0xfffffe0106df15c0
crypto_dispatch_one() at crypto_dispatch_one+0xde/frame 0xfffffe0106df15e0
ovpn_udp_input() at ovpn_udp_input+0x492/frame 0xfffffe0106df1690

From the backtrace it looks like that something in OpenVPN got messed up.
Could it be that the OpenVPN daemon did not get restarted after the update?
I'm using DCO so maybe the kernel driver and the binary did not match.
It is just an idea.

Best regards
Timmi

Looks like an issue with DCO indeed.  I don't see any pending fixes in FreeBSD's stable/14 so if this keeps happening I can only recommend you turn it off.


Cheers,
Franco

Hi Franco,

thank you very much for the reply.

DCO is running since 21st of January 2026 on our instance without such a crash.

I noticed with the update from 26.1.1 to 26.1.2 the IP assignment from the VPN was not reset like it is happening after a reboot of the OPNsense.
I just checked the logs and I would say the OpenVPN server have not been restarted during the update. Even so there was the update to OpenVPN 2.6.19.

I could imagine that this could cause such strange issues.

> 21st of January 2026

I don't think that's a long enough period to tell. I've seen fixed every other month that fix an obvious crash or misbehaviour from upstream, but nothing pending at the moment. I think this is one that hasn't been found (or needed to be fixed elsewhere). Might want to wait for FreeBSD 15.1 to be included in 26.7 and try again. Some fixes never make it to FreeBSD 14 anymore.


Cheers,
Franco

OK understood.
I will keep monitoring it.

So you don't think that the missing restart to the service after the update could not be the root cause?