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 35997EB64D7 for ; Mon, 26 Jun 2023 14:48:38 +0000 (UTC) Received: by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 418f1fe3; Mon, 26 Jun 2023 14:43:16 +0000 (UTC) Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [2607:f8b0:4864:20::d36]) by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTPS id 755315dc (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Wed, 17 May 2023 23:13:25 +0000 (UTC) Received: by mail-io1-xd36.google.com with SMTP id ca18e2360f4ac-76fe17da95fso33092139f.2 for ; Wed, 17 May 2023 16:13:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684365203; x=1686957203; h=content-transfer-encoding:subject:content-language:from:to :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=zp7hI/a0wxrB6sgVQa04D8nK6P2oVwfSviKxbM22VU4=; b=QNIuVHiuLr36+LFoZ6mYe4OTSkr36DLyAqZl0e1HTbMHELpDmCxvvbFGuN1+uad4GM VTwPSEWyEs9sgipCC+bTq8xYRKeDjBp8nZ9V+/UyEUJFuxU258WU+4PRfhi1HjGLimKR nM/f+XqC3der3HnUAzf9r7bOBU4cHflfJPnuvrXwbkYsXCzmNkrdw3TabTGIXJURLmSQ nZh+h3aCdWJpwYDevpokI7KbWgBtLnRZ+NiRY+S4Kj3bSRTZIwoJzTJsirf4RLcDSpt/ rFgg+Ayr9BH8ayYDjxRDKT1bIMuAhipX+GxlCgEcHBYghK1xFmeHzGRq2vaC6Ze2ljF+ ZEtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684365203; x=1686957203; h=content-transfer-encoding:subject:content-language:from:to :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=zp7hI/a0wxrB6sgVQa04D8nK6P2oVwfSviKxbM22VU4=; b=h77n1jAKc73oz8vjABa9xB6BZqWZ/aBNXBhplCIYfHxOCE9/X5lH4nxJCU0HcF67+r 7dDFKrW6nBdbb7C4SCv5ZRQkBMSsjiENrlx55verHbrnkyjZnVltjvlZBFmBmZYJ0oxM CVBia0ZFoNv+ayFL6CnImaOmlTw2+Clb93WeIAKUg/tnu8L/jh7oh6Fhn+JTrEbUmD08 9+cpGHQWS1x4rGYEGwY0HKqlFaKAD/HlIrTIua7P3iagvLg4A5APF8vwcjT1rtVmLTjZ mlBKIxz/fLSuL1/S+P6+oMc8k1ElIDCc3dO+9DTQih4snVWcXPFUC7Jdm/qM+P+6qHtB HfTg== X-Gm-Message-State: AC+VfDxLcuAj7WIJaQwVqO3Az1a2kOhCfew2mxv5WU7GOZPoZsMLQMnb uNIYqc6MvwYvOQcfA3JNfhbE/2NRYTU= X-Google-Smtp-Source: ACHHUZ6BLF3djwr+yILkMSuMtshU9TmJ6kZn0DPa7NCXO65P0nWgI2gnCcEKc826CYzpUwSdJSRzng== X-Received: by 2002:a5d:9e50:0:b0:76d:6398:e6f0 with SMTP id i16-20020a5d9e50000000b0076d6398e6f0mr5743557ioi.12.1684365203530; Wed, 17 May 2023 16:13:23 -0700 (PDT) Received: from [10.12.114.193] ([172.58.83.91]) by smtp.gmail.com with ESMTPSA id z26-20020a6be21a000000b0076fc5340aa3sm23244ioc.40.2023.05.17.16.13.22 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 May 2023 16:13:23 -0700 (PDT) Message-ID: <4fd6c9cb-c2cf-7a16-ee62-d958790652ea@gmail.com> Date: Wed, 17 May 2023 18:13:21 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 To: wireguard@lists.zx2c4.com From: Harry G Coin Content-Language: en-US Subject: ip netns del zaps wg link Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Mon, 26 Jun 2023 14:43:07 +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" First, Hi and thanks for all the effort! At least on Ubuntu latest LTS:  As advertised, if a wireguard link gets created by systemd/networkd, then set into a different net namespace, all works well. However, if that namespace is deleted, the link appears to be 'gone forever'.  Other link types reappear in the primary namespace when the namespace they are in gets deleted.   I'm not sure whether the link retains its 'up' or 'down' state when the namespace it's in gets deleted and reset to primary.  Not a big deal, doesn't happen often. This is 100% repeatable.   Some other answer than 'inaccessible until the next reboot' would be nice.