What is the proper way to handle the wireguard module now that it's part of the base system?
Date: Wed, 12 Apr 2023 15:26:28 UTC
I just upgraded to FreeBSD 13.2-RELEASE and made sure to deinstall the net/wireguard-kmod package before I rebooted. I had to force deinstall it since it's still a dependency to net/wireguard. No problems though - VPN-tunnel is up with the base kernel module and seems to be working just fine. A few questions though: 1) What happens if there are two identically named modules on the system - one in /boot/kernel and the other in /boot/modules? Which one gets priority and can this be controlled? 2) Depending on the answer to question 1, should I perhaps have left net/wireguard-kmod in place? If not, shouldn't there be a check in the Makefile for net/wireguard so it doesn't pull in net/wireguard-kmod as a dependency on FreeBSD 13.2? Regards Morgan Wesström