Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit@transpect.com>
To: Aaron Jones <aaronmdjones@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: What are the options for stopping and starting?
Date: Mon, 4 Dec 2017 13:37:53 -0500	[thread overview]
Message-ID: <20171204183753.GA5311@black.transpect.com> (raw)
In-Reply-To: <0e21b9be-bb38-427c-629b-a45473d6e223@gmail.com>

Hi Aaron,

Yes, removing the link should disable it. But that's overkill. Assuming I
want to leave the device in place, and the IP assignments there for
subsequent use by WireGuard, is there a simple way to shut WireGuard off,
without tearing down more than required?

If I'm running a VPN on a tun or tap device, for instance, I don't have to
remove the device to turn the VPN software off. I'm looking for the minimal,
not maximal, way to do that with WireGuard -- the equivalent to shutting
down a daemon in user space.

Thanks,
Whit

On Mon, Dec 04, 2017 at 05:31:35PM +0000, Aaron Jones wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 04/12/17 17:29, Whit Blauvelt wrote:
> > Is there a preferred way to take WireGuard fully down? We could
> > unload the wireguard (and ip6_udp_tunnel and udp_tunnel?) modules.
> > But that seems a crude method. What's perferred? I see we can "set
> > <interface> remove", but is there a simple command to take them all
> > down? (One could obviously be scripted; just wondering if I'm
> > missing that one's already there.)
> 
> # ip link del dev wg0
> 
> Regards,
> Aaron Jones

  reply	other threads:[~2017-12-04 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 16:01 Whit Blauvelt
2017-12-04 16:14 ` Jason A. Donenfeld
2017-12-04 17:29   ` Whit Blauvelt
2017-12-04 17:31     ` Aaron Jones
2017-12-04 18:37       ` Whit Blauvelt [this message]
2017-12-04 18:49         ` Jason A. Donenfeld
2017-12-04 18:06     ` Jason A. Donenfeld
2017-12-04 19:27       ` Whit Blauvelt
2017-12-04 19:36         ` Jason A. Donenfeld
2017-12-04 17:00 ` Aaron Jones

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=20171204183753.GA5311@black.transpect.com \
    --to=whit@transpect.com \
    --cc=aaronmdjones@gmail.com \
    --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).