Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Harry G Coin <hgcoin@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>, wireguard@lists.zx2c4.com
Cc: maarten@de-vri.es
Subject: Re: ip netns del zaps wg link
Date: Sat, 15 Jul 2023 15:29:25 -0500	[thread overview]
Message-ID: <c210924e-71f2-2243-dbf3-ef7a202a7661@gmail.com> (raw)
In-Reply-To: <45a9cfad-7d77-1be7-9e38-165d12a31c08@tls.msk.ru>


On 7/14/23 23:48, Michael Tokarev wrote:
> 15.07.2023 00:48, Harry G Coin wrote:
> ..
>
>> [] allowing wireguard interfaces to behave like all other interfaces 
>> when a namespace is destroyed  (moving back to the namespace where it 
>> was born and to which it retains connection anyhow) 
>
> The thing is that all interface types behave like this when a network 
> namespace is removed:
> they're destroyed together with the namespace.  All which can be 
> deleted anyway, for which
> an `ip link del' command works, - like, physical NICs are the only 
> exception here b/c you
> can't remove a physical NIC from a physical machine this way.
>
> So in this context, wg interfaces are *already* behaving like all 
> other virtual interfaces,
> and this is done by linux network/namespace subsystem, not by wireguard.
>
> /mjt


Oh dear.    It sure makes more sense to me for anything called 'an 
interface' to move in the same fashion as any other.  Having to 'just 
know' which ones will 'remain' and which ones will 'go away and need to 
be entirely reconfigured all the time' seems more than the security need 
calls for.  Just setting the link down when the netns goes away would be 
better, I can decide when, whether and how to create and destroy 
interfaces.   Or at least an option to 'treat all links the same when 
the netns goes away' somehow.

Off soap box now!

Thanks for the comments.



      reply	other threads:[~2023-07-15 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 23:13 Harry G Coin
2023-07-14 10:27 ` Maarten de Vries
2023-07-14 21:48   ` Harry G Coin
2023-07-15  4:48     ` Michael Tokarev
2023-07-15 20:29       ` Harry G Coin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c210924e-71f2-2243-dbf3-ef7a202a7661@gmail.com \
    --to=hgcoin@gmail.com \
    --cc=maarten@de-vri.es \
    --cc=mjt@tls.msk.ru \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).