From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Bzzzz <lazyvirus@gmx.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Many users
Date: Sun, 6 Aug 2017 22:22:28 +0200 [thread overview]
Message-ID: <CAHmME9op6iHuOxRHaRvgmKetoMEM1RtY=x7S_Fug=6m6CpWGfg@mail.gmail.com> (raw)
In-Reply-To: <20170806210237.4dbbed42@msi.defcon1>
Hey Jean-Yves,
There's an artificial limitation of 65535 peers per interface. This
limitation isn't _entirely_ necessary, and if it becomes a problem for
folks, I could remove it.
There was somebody on this list who set up thousands of peers and
thousands of interfaces a while ago, and after handling some issues
with him, things worked pretty well.
So, to answer your question: WireGuard should scale quite well, and
you shouldn't have many problems. But of course let me know if you do.
Jason
next prev parent reply other threads:[~2017-08-06 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 19:02 Bzzzz
2017-08-06 20:22 ` Jason A. Donenfeld [this message]
2017-08-06 20:34 ` Bzzzz
2017-08-06 20:57 ` Jason A. Donenfeld
2017-08-06 21:10 ` Bzzzz
2017-08-07 19:05 ` Jason A. Donenfeld
2017-08-07 19:13 ` Bzzzz
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='CAHmME9op6iHuOxRHaRvgmKetoMEM1RtY=x7S_Fug=6m6CpWGfg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=lazyvirus@gmx.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).