hw-probe VS plugins

You could also use the app/site of hw-probe https://github.com/linuxhw/hw-probe/blob/master/INSTALL.md

That's all the more reason to add more samples. Oh, the joys of open-source!

You could try installing Hardware Probe to further check. Plus, could you send the output of lspci in command line.

The drm-legacy mentioned above is an issue with the website and/or database: https://github.com/linuxhw/hw-probe/issues/137.

Make the probe

The report is based on all community hardware probes since 2014.

'Detected' means 'Device is detected, driver is found, but not tested', see https://github.com/linuxhw/hw-probe#operability

See https://github.com/linuxhw/hw-probe/blob/master/INSTALL.BSD.md

Side note: d= in URLs at the website for BSD hardware · Issue #112 · linuxhw/hw-probe, so let's adapt the three previously given URLs, to include d=FreeBSD:

Previously, when primary WAN resets, Wireguard would jump onto failover, but not jump back once primary was restored. This is a problem when failover shouldn't be used except for emergencies, e.g. it has limited traffic. This is issue 3325.

plugins: os-crowdsec 1.0.5[1]

But the latest ddclient plugin still has a bug that will keep spamming DuckDNS every 5 minutes: https://github.com/opnsense/plugins/issues/3344. So I still keep using the old dydns plugin for now.

You might have better luck putting in an issue here: https://github.com/opnsense/plugins

So, I have a feeling the answer can be found at https://github.com/opnsense/plugins/tree/master/net/zerotier, but I cannot make sense of what is there.

plugins: os-acme-client 3.16[1]

plugins: os-haproxy 4.1[1]

Someone Reported - https://github.com/opnsense/plugins/issues/3267

AFAIK Unbound does not support it but BIND plugin does (https://github.com/opnsense/plugins/blob/master/dns/bind/pkg-descr), so: