From: Der PCFreak <mailinglists@pcfreak.de>
To: wireguard@lists.zx2c4.com
Subject: Peer names in configuration file possible?
Date: Tue, 22 Jan 2019 12:50:17 +0100 [thread overview]
Message-ID: <ba2eee20-4dcd-2601-ffb7-bd1915230b0e@pcfreak.de> (raw)
Hi,
this is my first post to this list, so hopefully I don't get anything
wrong. Excuse me if so.
I don't know if this has ever been mentioned but I am asking myself how
should I keep track of let's say 1000 Peers in the configuration file of
a WireGuard server when the config file just shows me the public key of
the peers to identify them?
Would it be possible to add something like 'identifier' which might or
might not be unique:
Sample '/etc/wireguard/wg0-server.conf'
[Interface]
...
...
[Peer]
identifier=computer01
...
...
[Peer]
identifier=computer02
...
...
For example the command 'wg show wg0-server dump' could then maybe show
the 'identifier' as column to make things easier?
I am thinking of possibly replacing/migrating a large OpenVPN server
instance to WireGuard and I am currently thinking about the management of
the peers which on OpenVPN I do do with username/password + OTP. Just
the public key in the config is not enough in my opinion, a descriptive
field should be possible.
Also I assume when 'SaveConfig = true' is set in the servers
configuration file any saves to the file currently remove manually added
comments so doing it with comments is not a good option.
Regards
Peter aka PCFreak
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev reply other threads:[~2019-02-17 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 21:59 Request for review: Add a short name attribute to peers for human friendly output Jaseem Abid
2019-01-22 11:50 ` Der PCFreak [this message]
2019-02-21 21:11 ` Peer names in configuration file possible? Ivan Labáth
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=ba2eee20-4dcd-2601-ffb7-bd1915230b0e@pcfreak.de \
--to=mailinglists@pcfreak.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).