From: Damian Kaczkowski <damian.kaczkowski+wireguard.lists@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [patch] add support for peer names using a file in userspace
Date: Thu, 01 Mar 2018 15:36:34 -0000 [thread overview]
Message-ID: <CAGzienE4uVUo9BEEpQKmoD2vgqtzQQDBOo=h_vMJejxQF5kNzQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rV3simg0dTD7ja-RGWGTSR0dSMgJ20ft1FXPeZyFWamw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
On 8 December 2017 at 19:45, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Absolutely not. If something like this lands, it will be called
> "Description=" or the like, as another attribute of a peer. There's no
> reason to make the section parser more complicated, when this is
> essentially just another key value.
+1.
Description, Comment, or maybe Name would be handy.
I got > 200 peers. I am getting hard times checking for peer status.
It would be nice to be able to do something like this:
wg | grep -A6 -B6 my_Description_or_Comment
Or maybe even simpler:
wg show peer by_Name
To show current status of selected peer.
[-- Attachment #2: Type: text/html, Size: 5540 bytes --]
prev parent reply other threads:[~2018-03-01 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 15:31 [patch] wg: " Lonnie Abelbeck
2017-12-08 4:23 ` Jason A. Donenfeld
2017-12-08 4:26 ` Jason A. Donenfeld
2017-12-08 13:42 ` [patch] " Lonnie Abelbeck
2017-12-08 18:45 ` Jason A. Donenfeld
2017-12-08 19:00 ` Lonnie Abelbeck
2017-12-08 20:39 ` Jason A. Donenfeld
2017-12-09 1:09 ` Eric Light
2017-12-09 11:32 ` Matthias Urlichs
2018-03-01 15:36 ` Damian Kaczkowski [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='CAGzienE4uVUo9BEEpQKmoD2vgqtzQQDBOo=h_vMJejxQF5kNzQ@mail.gmail.com' \
--to=damian.kaczkowski+wireguard.lists@gmail.com \
--cc=Jason@zx2c4.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).