OPNsense Forum
Archive => 20.1 Legacy Series => Topic started by: dougmeredith on February 26, 2020, 07:31:43 pm
-
I thought I was mere hours away from putting my first OPNsense instance into production, but things don't always work out that way. lol
* OPNsense 20.1.1-amd64
* All updates have been applied
* Hyper-V generation 2 VM
* VM host has mirrored disks and ECC RAM
* No problems with any other VMs on the same host
The file good.xml is a /conf/config.xml that works fine. bad.xml is the next iteration, with hardly any changes, that consistently causes a kernel panic. Kernel dump as attached.
I have no experience interpreting kernel dumps, but it seems very unlikely that this is a hardware problem. Any thoughts or advice appreciated.
-
Do you have WireGuard installed?
-
I have the wireguard and wireguard-go packages installed, but not the plugin.
-
I had read of past issues with WireGuard, and at one point in my testing I uninstalled the packages, and was still getting the kernel panic. That was before I isolated the config change causing the problem, so I can't claim that that was reproducible.
-
Either remove WireGuard or disable shared forwarding to fix the panics
-
The help is much appreciated. Can you direct me to some information on the issue? I saw posts about kernel panic problems with WireGuard from several months ago, but had the impression that this had been resolved. Also, despite a web search, I'm unclear what you mean by "shared forwarding".
-
Firewall:Settings:Advanced .. shared forwarding. Try to disable
-
I've just tested, and you are quite correct. Removing WireGuard stops the panics, as does disabling shared forwarding. For anyone else encountering this, the problem is described [here][https://github.com/opnsense/src/issues/52]. Thanks for your help!