From: ST <smntov@gmail.com>
To: Kalin KOZHUHAROV <me.kalin@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: add/remove a peer
Date: Mon, 26 Mar 2018 18:13:52 +0300 [thread overview]
Message-ID: <1522077232.2044.31.camel@gmail.com> (raw)
In-Reply-To: <CAKXLc7e1cJ6E=KCMshe_=EOtnwTa-YpRwPe2RwW8vNkj3qzONw@mail.gmail.com>
On Sun, 2018-03-25 at 21:17 +0200, Kalin KOZHUHAROV wrote:
> On Sun, Mar 25, 2018 at 8:10 PM, ST <smntov@gmail.com> wrote:
> > PS: if you have over 100 peers it is a bit a headache to find a free IP
> > when adding a new peer. There is no reason WG could not scan through IPs
> > it already knows and choose a free one, assign it in its own config file
> > and print it out for passing to the remote peer...
> >
> There is a reason, at least one, good one - it is called simplicity.
> It is also hard to work when you are running out of disk space or
> memory; do you expect WG to solve that for you?
They are not related to WG at all.
> Simply put, IP addressing schemes are not a part of WG, neither a requirement.
> There are many ways to use WG and "assign random, free IP address and
> send to a new peer" is too specific of a use case.
No, sending to a peer is not what I asked - only assign a random free IP
if no one is provided to `wg set peer ...`. That's it. Only locally and
only internally. No keys distribution schemes or something. How to send
it to the new peer is the problem of the sysadmin. Could be per
encrypted email/https or whatever.
> What happens when you run out of addresses?
You just give an error message "no more IPs are available, make one free
or choose another IP range!"
> How do you re-assign an IP address to a new peer?
You delete the [Peer] with that IP from the .conf file (or `wg set wg0
peer peer_pubkey remove`) and then `wg set peer allowed-ips
old.ip.to.reassign/32 ...`
Thank you!
next prev parent reply other threads:[~2018-03-26 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 19:32 add/remove a peer ST
2018-03-25 16:43 ` Wang Jian
2018-03-25 17:57 ` ST
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 [this message]
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=1522077232.2044.31.camel@gmail.com \
--to=smntov@gmail.com \
--cc=me.kalin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.