add/remove a peer
smntov at gmail.com
Mon Mar 26 17:13:52 CEST 2018
On Sun, 2018-03-25 at 21:17 +0200, Kalin KOZHUHAROV wrote:
> On Sun, Mar 25, 2018 at 8:10 PM, ST <smntov at 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
More information about the WireGuard