From: Derrick Lyndon Pallas <derrick@pallas.us>
To: Barrett Strausser <barrett@bossanova.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: CryptoKey Routing Management for Peers
Date: Fri, 14 Feb 2020 15:40:33 -0800 [thread overview]
Message-ID: <1FB426DC-C314-4DBE-BEF9-2A35D49094C4@pallas.us> (raw)
In-Reply-To: <CA+w0pKY0KGCBAPYqoTReXdDmB22ctWkczEoK-FFxoR3B8b0wzw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1217 bytes --]
You might also want to check out https://pypi.org/project/wgnlpy/ which is a Wireguard configuration library for python.
~Derrick • iPhone
> On Feb 14, 2020, at 3:02 AM, Barrett Strausser <barrett@bossanova.com> wrote:
>
>
> I don't doubt that it can handle 1M peers.
>
> My question was more concerned with can an Organization perform the configuration management to handle 1M peers if all configuration is through a static IP.
>
> If I have 1M peers and .9999 have no change per day, that still leaves 100 changes or ~4 per hour. I'd argue it is a good practice to have to restart services to pick up those changes.
>
> I'll have a look at those links. Thank you very much
>
> -b
>
>
>
>> On Sat, Feb 8, 2020 at 4:29 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>> WireGuard has an API, via Netlink. This might help you:
>>
>> https://git.zx2c4.com/wireguard-tools/tree/contrib/embeddable-wg-library
>> https://git.zx2c4.com/wireguard-tools/tree/src/uapi/linux/wireguard.h
>>
>> It can handle 1M peers, yes.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
[-- Attachment #1.2: Type: text/html, Size: 2206 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-02-14 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 16:23 Barrett Strausser
2020-02-08 21:29 ` Jason A. Donenfeld
2020-02-10 14:07 ` Barrett Strausser
2020-02-14 23:40 ` Derrick Lyndon Pallas [this message]
2020-02-15 0:13 ` Mo Balaa
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=1FB426DC-C314-4DBE-BEF9-2A35D49094C4@pallas.us \
--to=derrick@pallas.us \
--cc=barrett@bossanova.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).