From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Request: Optional "Comment" [Peer] entry
Date: Fri, 17 Nov 2017 09:29:40 +0100 [thread overview]
Message-ID: <bc1166f7-1a95-85ae-a528-700655f5ef1f@urlichs.de> (raw)
In-Reply-To: <1510906834.6309.77.camel@gmx.de>
On 17.11.2017 09:20, Manuel Schölling wrote:
> You could also use it for naming peers, i.e. using "Peer-(?P<name>[A-Za-z0-9\-]+)".
The usual way is to use a space as separator, i.e.
[Peer uplink]
This solves the naming issue. Nevertheless, a Comment= entry would also
be a good idea.
Also, after adding names we should use them as primary peer identifiers,
instead of their pubkeys.
--
-- Matthias Urlichs
next prev parent reply other threads:[~2017-11-17 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 10:04 disabling ipv6 with wg-quick ds
2017-11-16 11:22 ` Greg KH
2017-11-16 12:28 ` Jason A. Donenfeld
2017-11-16 20:31 ` Request: Optional "Comment" [Peer] entry Lonnie Abelbeck
2017-11-17 8:20 ` Manuel Schölling
2017-11-17 8:29 ` Matthias Urlichs [this message]
2017-11-17 9:20 ` Jason A. Donenfeld
2017-11-17 13:07 ` Antonio Quartulli
2017-11-20 10:58 ` disabling ipv6 with wg-quick ds
2017-11-17 11:34 Request: Optional "Comment" [Peer] entry Michael Keuter
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=bc1166f7-1a95-85ae-a528-700655f5ef1f@urlichs.de \
--to=matthias@urlichs.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).