From: Linus Nordberg <linus@nordberg.se>
To: wireguard@lists.zx2c4.com
Subject: Re: Dealing with large number of IPv4 clients
Date: Sat, 23 Mar 2019 11:56:09 +0100 [thread overview]
Message-ID: <877ecprh9y.fsf@nordberg.se> (raw)
In-Reply-To: 1RaAYaEHv_QRKUXdQO3U-bVTh2ZRb_kfhN62pX42RFyL_Jq_Y0Shl1V2t8s665ddlQpXQ80NBzQ4Bi5CUql18GkiZbunLbtDX1qz6yZbWkw=@protonmail.com
David Weinberger <cubicalpie@protonmail.com> wrote
Thu, 21 Mar 2019 12:35:05 +0000:
> What's the proper way to deal with large number of IPv4 clients?
>
> (We're aware of the wg-dynamic project, but it seems it's IPv6 only.)
wg-dynamic will support dynamic IP address allocation for both IPv4 and
IPv6.
It will use a link local IPv6 address for communications between client
and server daemons. Maybe this can explain the misconception that it
would be handling IPv6 addresses only?
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-03-23 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 12:35 Dealing with large number of IPv4 clients David Weinberger
2019-03-23 10:56 ` Linus Nordberg [this message]
2019-03-25 21:08 ` Matthias Urlichs
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=877ecprh9y.fsf@nordberg.se \
--to=linus@nordberg.se \
--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).