I'm not entirely sure if this is the root of my problem but I noticed that when migrating an Opnsense router from a node on a source cluster to a node on a destination cluster, Opnsense will lock up and can only be revived with a reboot of the VM. Looking at the VM console, Opnsense spams many errors about packets and MAC addresses etc.
This does not happen when I migrate that same VM between nodes on the same cluster and I see the default when doing so is to have Conntrack state enabled. Conversely, when migrating using PDM, you will see the warning "conntrack state migration not supported or disabled, active connections might get dropped". Does this mean the feature will never be implemented since it is technically impossible or that it may be added at a future release.
Apologies if this has been answered elsewhere before. I did search this forum and did not see a similar question asked.
This does not happen when I migrate that same VM between nodes on the same cluster and I see the default when doing so is to have Conntrack state enabled. Conversely, when migrating using PDM, you will see the warning "conntrack state migration not supported or disabled, active connections might get dropped". Does this mean the feature will never be implemented since it is technically impossible or that it may be added at a future release.
Apologies if this has been answered elsewhere before. I did search this forum and did not see a similar question asked.