Development discussion of WireGuard
 help / color / mirror / Atom feed
From: ST <smntov@gmail.com>
To: Wang Jian <larkwang@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: add/remove a peer
Date: Sun, 25 Mar 2018 20:57:36 +0300	[thread overview]
Message-ID: <1522000656.2044.8.camel@gmail.com> (raw)
In-Reply-To: <CAF75rJBe8amfHP__gQMzAf6cBj933c2yCg4wx4nA2hw98tcVXQ@mail.gmail.com>

On Mon, 2018-03-26 at 00:43 +0800, Wang Jian wrote:
> 2018-03-25 3:32 GMT+08:00 ST <smntov@gmail.com>:
> > Hello,
> >
> > I'm learning WireGuard and have a question regarding adding/removing a
> > peer.
> >
> > Is there something like:
> >
> > 1) wg add peer ABCDEF... allowed-ips 192.168.88.0/24 endpoint
> > 209.202.254.14:8172
> 
> 
> >
> > 2) similar for removing clients:
> >
> > wg rm peer ABCDEF...
> > or
> > wg rm peer allowed-ips 192.168.88.4/32
> >
> > Is this implemented already or should I file it as a feature request
> > somewhere? (if so - where?)
> >
> 
> You should already read man pages  (man wg).
> 
> for adding peer
> # wg set wg0 peer peer_pubkey allowed-ips 192.168.88.4/32 endpoint
> 209.202.254.14:8172

I want a WG (server) to assign an IP to a peer *automatically* if
allowed-ips is not provided when running `wg set wg0 peer`. And then
output it to STDOUT, so it can be passed to the peer (client). The same
can be done if peer's public key is not provided.
This would make addition of new peers(clients) much more easy - both for
sysadmins and for non-tech-savvy clients (the latter will get a ready
made wg0.conf file that they need to save to /etc/wireguard/ and all
they need to do is `wg-quick up wg0`. That's it.)

I don't think it is implemented...

Mr. Donenfeld - would this qualify as a feature request?

Thank you!

  reply	other threads:[~2018-03-25 17:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-24 19:32 ST
2018-03-25 16:43 ` Wang Jian
2018-03-25 17:57   ` ST [this message]
2018-03-25 18:10   ` ST
2018-03-25 19:17     ` Kalin KOZHUHAROV
2018-03-25 19:42       ` Roman Mamedov
2018-03-26 15:13       ` ST
2018-03-26 18:46 ` Luis Ressel
2018-03-26 19:48   ` ST

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=1522000656.2044.8.camel@gmail.com \
    --to=smntov@gmail.com \
    --cc=larkwang@gmail.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).