From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.zx2c4.com (lists.zx2c4.com [165.227.139.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 7623DC433FE for ; Mon, 21 Mar 2022 19:34:52 +0000 (UTC) Received: by lists.zx2c4.com (OpenSMTPD) with ESMTP id 113ea058; Mon, 21 Mar 2022 19:34:51 +0000 (UTC) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by lists.zx2c4.com (OpenSMTPD) with ESMTPS id 36fb147f (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO) for ; Wed, 16 Mar 2022 21:10:47 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id D2EB332008FA for ; Wed, 16 Mar 2022 17:10:44 -0400 (EDT) Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Wed, 16 Mar 2022 17:10:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=ZoR+rR1gtfmqyPHRmKnb5d36g/2ev+Jd3Xv3OSp3o nQ=; b=aTFPDTSnG7g6cPBUWtQFLCbBgxRAc8A5fBQptf3IUngKRw5QWfXLAWr+U UVmHxVCfPtxk0ZSUKTwa+dviOretYTab7caG5RWonxvOZZGLfUgw1UQS4d4yU6+U YAnhMHxA5/CRgLrMEV7AGE5LB5a8tppQXR0CI4tDy2muyxAc6E/FVpLwhz/7MkBP H5wedu/kxmQPnixGZWKf4Z1vfUGtx/5J9PHHll6TEpnawCkp/WGX928GJbpIUN/a +2qXCb+LranLAtVW4+DhBSSFMAz37aoJpgaX/3orrCZFpC/ePesuGf6wcKtg4K2t JgGOrnAlGzz1bDu+ZXs1Yi/aq94bQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudefvddgudegfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdefhedmnecujfgurhepof gfggfkfffhvffutgesthdtredtreertdenucfhrhhomhepvhhviihvlhgrugcuoehmrghi lhesvhhviihvlhgrugdrgiihiieqnecuggftrfgrthhtvghrnhepgefhfeekkeeltdegue eukeegtdegffettefhjeelvefhtdejhfeiiefhledtleefnecuffhomhgrihhnpeiigidv tgegrdgtohhmpdgurhhophgsohigrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhgrihhlsehvvhiivhhlrggurdighiii X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 215233C031B; Wed, 16 Mar 2022 17:10:44 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-4907-g25ce6f34a9-fm-20220311.001-g25ce6f34 Mime-Version: 1.0 Message-Id: Date: Thu, 17 Mar 2022 00:10:21 +0300 From: vvzvlad To: wireguard@lists.zx2c4.com Subject: Bug in the macOS client wireguard: make disable the tunnel from the context menu impossibility Content-Type: text/plain X-Mailman-Approved-At: Mon, 21 Mar 2022 19:34:47 +0000 X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.30rc1 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" In your repository (https://git.zx2c4.com/wireguard-apple/) I have not found a githab or something similar, where I could leave an issue, so I write to the post, as I was advised by one of the committers. I am actively using WG client on my apple devices, and if the ios-clients work fine, with macos versions I have problems from time to time, so I want to point them out to developers. Here is, for example, one of the problems: https://www.dropbox.com/s/4bit2xem8g1wmk8/Screen%202022-03-13%20at%2017.59.43.mov?dl=0 If the option "on demand" is enabled, then after disconnecting the tunnel from the context menu or from the system settings, it immediately reconnects. If the respected developers are interested, I could describe the reproduction of some of these kinds of problems and give some thoughts on usability (I compare it to warp, which is very nice to use).