From: "Manuel Schölling" <manuel.schoelling@gmx.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Request: Optional "Comment" [Peer] entry
Date: Fri, 17 Nov 2017 09:20:34 +0100 [thread overview]
Message-ID: <1510906834.6309.77.camel@gmx.de> (raw)
In-Reply-To: <7777F2EF-1D1B-4403-91C6-FB4A36C92CC5@lonnie.abelbeck.com>
I like the idea of comments!
And while we're at it: having multiple [Peer] section in incompatible
with most other config parsing tools (e.g. python std library's
configparser [1]).
Maybe we could allow the peer section names to be of the form "Peer[A-
Za-z0-9\-]*" or something?
You could also use it for naming peers, i.e. using "Peer-(?P<name>[A-
Za-z0-9\-]+)".
Bye,
Manuel
[1] https://docs.python.org/3.5/library/configparser.html
On Thu, 2017-11-16 at 14:31 -0600, Lonnie Abelbeck wrote:
> I have a suggestion, feature request ...
>
> With several peers, the output of "wg show" is difficult to visually
> identify the peers at a quick glance.
>
> How about an optional "Comment = " entry for the [Peer] section.
>
> For Example:
> --
> [Peer]
> PublicKey = UMJMPFVTzjmzr7SJMQ7k+Z+3Pr1aq4w+5chtUny6Akg=
> Endpoint = [fda6:66b2:b74a:50::3]:51820
> AllowedIPs = 10.4.0.2/32
> Comment = pbx3 - Jetway NF9HG-2930
> --
>
> For each peer in "wg show" with a "Comment = " defined ...
> --
> peer: HIgo9xNzJMWLKASShiTqIybxZ0U3wGLiUeJ1PKf8ykw=
> endpoint: [fda6:662b:b74a:50::3]:51820
> allowed ips: 10.4.0.2/32
> latest handshake: 3 seconds ago
> transfer: 376 B received, 680 B sent
> comment: pbx3 - Jetway NF9HG-2930
> --
>
> If others like this idea, should the comment be displayed first,
> last, etc. ?
>
> Truncating the comment string to 64 characters would be fine. Or
> even 32 chars.
>
> Thoughts ?
>
> Lonnie
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2017-11-17 8:16 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 [this message]
2017-11-17 8:29 ` Matthias Urlichs
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=1510906834.6309.77.camel@gmx.de \
--to=manuel.schoelling@gmx.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).