From: Aaron Jones <aaronmdjones@gmail.com>
To: Whit Blauvelt <whit@transpect.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: What are the options for stopping and starting?
Date: Mon, 4 Dec 2017 17:31:35 +0000 [thread overview]
Message-ID: <0e21b9be-bb38-427c-629b-a45473d6e223@gmail.com> (raw)
In-Reply-To: <20171204172937.GA11936@black.transpect.com>
-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJaJYZ0AAoJEIrwc3SIqzASUeEQAJ1E1n6x7ytRQofgyph+FlJe
rRFBhilGwT0t6MPCj44rJTPoGbUWXWZm9EaO+2RXBcpaZpedKpBoyX2kAh92dzYo
TsyHba0uIgSjgZGxxAbDORd2lH0ayIMx+INk0TZFDgAVHLK1e0+rW8DhSwBw3HvY
DZ9q2DqzBZ3Fos1LGxc41u0asFS1tDR4f0lBOvY0m32kXVb/U/2jTJ0VpaaZjlS6
5GwZZQGnfokbE48ge+xydF1CxWhr1/TAF6VqUIGFwBCJL7xYJt3hbVcis2ynraZ+
T5pqlgIEwwIvKvVtUf7OTHm/5qj6zayAlTUdeZnWAcKaCB95+Vuxqdex8Szk832N
B6e3rfJLs8/5BXhKfZ0Pwty8SRzo8KhSVpERSla7p6Ti4eGOFX5rbJzJ4+Hgme+M
KdH4OKoLY3/6+9xjfrzpoFQDkk53Py7B+C2K273Mz206ctziLcGmX1zHD3gKoOZz
CLdKoCrhTUchRfnbWtGH9owyn/JsSwvR/1Slyzoz2U/fbj/MOqiUzoE4F3Cw/3iy
H37OuM2dZzDCxqNx6AQGdXCbFpOhdDAcA2gBPDMMl1uF/cgDhoK+O4oiuFEpXuGQ
4u+mnoLe+WI9PmxRsEgfnqtA1dk/8OT3/YoOSTFdHt0Cunz9F/tC9KA0EmRHzk7Z
O52oPQUlQVRYqnn2wC3y
=RyV9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-12-04 17:24 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 [this message]
2017-12-04 18:37 ` Whit Blauvelt
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=0e21b9be-bb38-427c-629b-a45473d6e223@gmail.com \
--to=aaronmdjones@gmail.com \
--cc=whit@transpect.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).