From nobody Tue Oct 08 01:38:39 2024 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XMzFV0Xskz5Yl7T for ; Tue, 08 Oct 2024 01:38:54 +0000 (UTC) (envelope-from polarian@polarian.dev) Received: from mail.polarian.dev (mail.polarian.dev [IPv6:2001:8b0:57a:2385::8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XMzFT162Cz4H7K for ; Tue, 8 Oct 2024 01:38:53 +0000 (UTC) (envelope-from polarian@polarian.dev) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=polarian.dev header.s=polarian header.b=Lgyfv1Yu; spf=pass (mx1.freebsd.org: domain of polarian@polarian.dev designates 2001:8b0:57a:2385::8 as permitted sender) smtp.mailfrom=polarian@polarian.dev; dmarc=pass (policy=reject) header.from=polarian.dev Received: from Hydrogen (_gateway [192.168.2.1]) by mail.polarian.dev (Postfix) with ESMTPSA id 504F410A0772 for ; Tue, 08 Oct 2024 01:38:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/relaxed; d=polarian.dev; s=polarian; t=1728351522; bh=3l5Rt+PFEXEsY57FXXy79txpY1Fp02qt/7yveMOB8cA=; h=Date:From:To:Subject:In-Reply-To:References; b=Lgyfv1YuL0u+Pgl7ExkgrsKsseR6EIc+pJABER92/lRVsciG0EDfzCRDfWNlAcxyl ImR0iKoqugVkhkE2TR+84tyYyXqwl4C4u96/HgHMFxRB+ofrTl6ZTUoLLBU+oIYwM/ +StkSJbm1PHveVUI8S2n4yMA3gIc5UI16TIqS0pk= Date: Tue, 8 Oct 2024 02:38:39 +0100 From: Polarian To: questions@freebsd.org Subject: Re: wireguard confusion Message-ID: <20241008023839.01b159e0@Hydrogen> In-Reply-To: References: X-Mailer: Claws Mail 3.20.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.40 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.995]; NEURAL_HAM_MEDIUM(-0.99)[-0.986]; NEURAL_HAM_LONG(-0.92)[-0.916]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[polarian.dev,reject]; R_DKIM_ALLOW(-0.20)[polarian.dev:s=polarian]; R_SPF_ALLOW(-0.20)[+ip6:2001:8b0:57a:2385::8]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20712, ipnet:2001:8b0::/32, country:GB]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[polarian.dev:+] X-Rspamd-Queue-Id: 4XMzFT162Cz4H7K X-Spamd-Bar: --- 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