Development discussion of WireGuard
 help / color / mirror / Atom feed
From: reiner otto <augustus_meyer@yahoo.de>
To: <wireguard@lists.zx2c4.com>
Subject: Re: Multiple (client-)peers with same keys possible ?
Date: Wed, 16 May 2018 05:22:05 +0000 (UTC)	[thread overview]
Message-ID: <896575027.3009605.1526448125867@mail.yahoo.com> (raw)
In-Reply-To: <896575027.3009605.1526448125867.ref@mail.yahoo.com>

Then individual keys for the clients, sigh.

Which leads to next question:
When adding a new client to the servers wg0.conf,
does it require a restart of wg, _OR_ is it safe to simply "edit" wg0.conf, adding the clients info ?

Cheers,
Reiner

 

       reply	other threads:[~2018-05-16  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <896575027.3009605.1526448125867.ref@mail.yahoo.com>
2018-05-16  5:22 ` reiner otto [this message]
2018-05-16 14:04   ` ajs124
     [not found] <267632710.2840000.1526409369057.ref@mail.yahoo.com>
2018-05-15 18:36 ` reiner otto
2018-05-15 20:50   ` Eric Light
2018-05-15 21:39     ` 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=896575027.3009605.1526448125867@mail.yahoo.com \
    --to=augustus_meyer@yahoo.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).