From: Nicolas Prochazka <nicolas.prochazka@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Some questions about wireguard
Date: Wed, 15 Feb 2017 11:12:08 +0100 [thread overview]
Message-ID: <CADdae-jq5UET3utsK=gzpWig=MK3ts2KjF7=UYbAec0_Y08MGQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
Hello,
wireguard seems very interesting for our deploiement.
We have some questions about it :
- how many tunnels a peer can manage ?
In our environnement, ~ 10 000 clients --> "server"|peer
- at this moment we are using , kcptun or v2ray , chinese udp tunnel, with
differents problem
bandwitch , latency ,
how wireguard manage this ( udp tunnel from kernel ? )
- about peer key management ?
with 10 000 peer keys, how can we manage it, use wg and a database for
example ?
To finish, wireguard seems to be very impressive, just the essential
thanks.
Regards,
Nicolas Prochazka
[-- Attachment #2: Type: text/html, Size: 700 bytes --]
next reply other threads:[~2017-02-15 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 10:12 Nicolas Prochazka [this message]
2017-02-17 13:48 ` Jason A. Donenfeld
2017-02-17 13:55 ` Nicolas Prochazka
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='CADdae-jq5UET3utsK=gzpWig=MK3ts2KjF7=UYbAec0_Y08MGQ@mail.gmail.com' \
--to=nicolas.prochazka@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).