From owner-freebsd-bugs@freebsd.org Mon Apr 5 15:22:02 2021 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2AF715BC8C2 for ; Mon, 5 Apr 2021 15:22:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4FDZBy04rbz4hyH for ; Mon, 5 Apr 2021 15:22:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id EF40D5BC6AD; Mon, 5 Apr 2021 15:22:01 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EEBAA5BC910 for ; Mon, 5 Apr 2021 15:22:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FDZBx5YqCz4j47 for ; Mon, 5 Apr 2021 15:22:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id AAD401AF6B for ; Mon, 5 Apr 2021 15:22:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 135FM1KG040454 for ; Mon, 5 Apr 2021 15:22:01 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 135FM1kF040453 for bugs@FreeBSD.org; Mon, 5 Apr 2021 15:22:01 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254795] Removing 'net/wireguard-kmod' also removes 'wireguard' even when 'net/wireguard-go' is desired Date: Mon, 05 Apr 2021 15:22:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jon@xyinn.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Apr 2021 15:22:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254795 Bug ID: 254795 Summary: Removing 'net/wireguard-kmod' also removes 'wireguard' even when 'net/wireguard-go' is desired Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: jon@xyinn.org Hello all, I'm currently running FreeBSD 12.2-RELEASE-p4 and have been keeping tabs on= the whole wireguard situation in FreeBSD. Today I ran an update and received the following message: Message from wireguard-2,1: -- For FreeBSD < 12.1 only the userland implementation wireguard-go is available. For FreeBSD >=3D 12.1 we default to use the kernel module if_wg(4). If you experience problems with it you can switch back to wireguard-go by removing net/wireguard-kmod and making sure net/wireguard-go is installed. The userland tools wg-quick(8) and wg(8) try to use kernel support if the kernel module is available and otherwise fall back to wireguard-go automatically. Config files are fully compatible. This makes sense, at the moment I don't feel comfortable running the kmod implementation until it has become more stable (Maybe I'll try it again in 6 months to 12 months). However, following the instructions above of removing= the 'net/wireguard-kmod' and making sure 'net/wireguard-go' is installed still attempts to remove the main 'wireguard' package, thus I won't be able to start/stop my existing wireguard services because of it (Unless I'm misunderstanding something). The example output from a clean slate is below: [root@octopus ~]# pkg install wireguard Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 3 package(s) will be affected (of 0 checked): New packages to be INSTALLED: wireguard: 2,1 wireguard-kmod: 0.0.20210323 wireguard-tools: 1.0.20210315_3 Number of packages to be installed: 3 Proceed with this action? [y/N]: y [1/3] Installing wireguard-tools-1.0.20210315_3... [1/3] Extracting wireguard-tools-1.0.20210315_3: 100% [2/3] Installing wireguard-kmod-0.0.20210323... [2/3] Extracting wireguard-kmod-0.0.20210323: 100% [3/3] Installing wireguard-2,1... =3D=3D=3D=3D=3D Message from wireguard-kmod-0.0.20210323: -- At this time this code is new, unvetted, possibly buggy, and should be considered "experimental". It might contain security issues. We gladly welcome your testing and bug reports, but do keep in mind that this code is new, so some caution should be exercised at the moment for using it in mission critical environments. =3D=3D=3D=3D=3D Message from wireguard-2,1: -- For FreeBSD < 12.1 only the userland implementation wireguard-go is available. For FreeBSD >=3D 12.1 we default to use the kernel module if_wg(4). If you experience problems with it you can switch back to wireguard-go by removing net/wireguard-kmod and making sure net/wireguard-go is installed. The userland tools wg-quick(8) and wg(8) try to use kernel support if the kernel module is available and otherwise fall back to wireguard-go automatically. Config files are fully compatible. [root@octopus ~]# pkg install net/wireguard-go Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: wireguard-go: 0.0.20210323,1 Number of packages to be installed: 1 The process will require 3 MiB more space. Proceed with this action? [y/N]: y [1/1] Installing wireguard-go-0.0.20210323,1... [1/1] Extracting wireguard-go-0.0.20210323,1: 100% [root@octopus ~]# pkg remove net/wireguard-kmod Checking integrity... done (0 conflicting) Deinstallation has been requested for the following 2 packages (of 0 packag= es in the universe): Installed packages to be REMOVED: wireguard: 2,1 wireguard-kmod: 0.0.20210323 Number of packages to be removed: 2 Proceed with deinstalling packages? [y/N]: y [1/2] Deinstalling wireguard-2,1... [2/2] Deinstalling wireguard-kmod-0.0.20210323... [2/2] Deleting files for wireguard-kmod-0.0.20210323: 100% [root@octopus ~]# service wireguard stop wg-quick: `wg0' is not a WireGuard interface [root@octopus ~]# Thank you! --=20 You are receiving this mail because: You are the assignee for the bug.=