Most have probably seen some things about this flair up. Best I can tell netgate hired a guy to port wireguard over to FreeBSD (glad they did). The netagate contractor did so, but rebuffed or ignored attempts from the wireguard founder to help and evaluate the port with first offer at least back in feb 2020. Port was finished internally and moved into freebsd 13 RC and the big marketing write ups from netgate after they released it backported to their freebsd 12.2 based pfSense 2.5.
then in a mad rush code review to vet this merge before FreeBSD 13 is released publicly the major brouhaha started and the netgate founder went on offense privately and publicly although less than they did against opnsense in years past.
pfsense 2.5 and the not yet released 2.5.1 candidates are still running the old implementation that was weighed, measured and found wanting by both the wireguard lead and FreeBSD security devs.
then in a mad rush code review to vet this merge before FreeBSD 13 is released publicly the major brouhaha started and the netgate founder went on offense privately and publicly although less than they did against opnsense in years past.
pfsense 2.5 and the not yet released 2.5.1 candidates are still running the old implementation that was weighed, measured and found wanting by both the wireguard lead and FreeBSD security devs.
In-kernel WireGuard is on its way to FreeBSD and the pfSense router
WireGuard probably won't make it into 13.0-RELEASE, but 13.1 seems very likely.
arstechnica.com