Re: wireguard confusion

Hello,

I am not sure about wg being in both base and the port.

However, I have a feeling it is because wireguard has two
implementations. You have the generic go implementation which runs in
the userspace which is developed and maintained by zx2c4 and other
contributors, this is within the port tree. However, there is also a
kernel module for in-kernel support for wireguard (see WG(4)) which
used to be in the port tree, but was moved into the base system at some
point (not sure when).

This is an educated guess, I assume it is because older FreeBSD
installs will not have the wireguard kernel module, and thus won't
ship wg in base, therefore wireguard-go would be used with
wireguard-tools which would provide wg. As /usr/bin is higher priority,
the wg within base is always used unless you explicitly invoke
/usr/local/bin/wg so no conflict should occur here, therefore works for
all FreeBSD versions, thats my best guess.

Take care,
-- 
Polarian
GPG signature: 0770E5312238C760
Jabber/XMPP: polarian@icebound.dev