From: Luis Ressel <aranea@aixah.de>
To: wireguard@lists.zx2c4.com
Subject: Re: wg showconf
Date: Sun, 5 Nov 2017 00:03:27 +0100 [thread overview]
Message-ID: <20171105000327.0a772771@vega.skynet.aixah.de> (raw)
In-Reply-To: <20171105000122.09eae100@vega.skynet.aixah.de>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
On Sun, 5 Nov 2017 00:01:22 +0100
Luis Ressel <aranea@aixah.de> wrote:
> Yes, wg does this. It's a deliberate design decision which is
> important to supporting roaming peers.
Whoops, sorry about that. Absentmindedly editing sentences without
reading the result is not a good idea. :)
Cheers,
Luis Ressel
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-04 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 20:04 Markus Woschank
2017-11-04 20:27 ` Luis Ressel
2017-11-04 21:25 ` Markus Woschank
2017-11-04 23:01 ` Luis Ressel
2017-11-04 23:03 ` Luis Ressel [this message]
2017-11-05 0:05 ` Markus Woschank
2017-11-06 16:06 ` Bruno Wolff III
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=20171105000327.0a772771@vega.skynet.aixah.de \
--to=aranea@aixah.de \
--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).