Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
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 00:42:12 +0500	[thread overview]
Message-ID: <20180326004212.55bf62f0@natsu> (raw)
In-Reply-To: <CAKXLc7e1cJ6E=KCMshe_=EOtnwTa-YpRwPe2RwW8vNkj3qzONw@mail.gmail.com>

On Sun, 25 Mar 2018 21:17:35 +0200
Kalin KOZHUHAROV <me.kalin@gmail.com> wrote:

> 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?
> 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.
> 
> May be you can cobble up something with a DHCP server that cares about
> certain address range?
> Or a simple flat-file dB and a script that does it for you?
> 
> What happens when you run out of addresses?
> How do you re-assign an IP address to a new peer?
> ...
> Those are questions widely outside WG, IMHO.

Agreed.

One more idea that comes to mind, is to use IPv6 and assign IPs based on peer
public keys. Assuming a fixed /64 subnet, using a 64-bit half of the public
key for the host part, still makes collisions nearly impossible.

-- 
With respect,
Roman

  reply	other threads:[~2018-03-25 19:30 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
2018-03-25 18:10   ` ST
2018-03-25 19:17     ` Kalin KOZHUHAROV
2018-03-25 19:42       ` Roman Mamedov [this message]
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=20180326004212.55bf62f0@natsu \
    --to=rm@romanrm.net \
    --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 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).