From: Nicolas Prochazka <nicolas.prochazka@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Some questions about wireguard
Date: Fri, 17 Feb 2017 14:55:11 +0100 [thread overview]
Message-ID: <CADdae-gZVqKC12_7zaqj1FVsjTe+6A8cuohjqM6fn5_DYRMBQw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9popejSYDF-yHB+FxX-dSo9PVqMwo-MOG7mQj56QiA4EQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
hello,
sorry for my english.
This question(udp tunnel ..) is not relevant, I learn a lot with the read
of mailing list.
Regards,
Nicolas
2017-02-17 14:48 GMT+01:00 Jason A. Donenfeld <Jason@zx2c4.com>:
> On Wed, Feb 15, 2017 at 11:12 AM, Nicolas Prochazka
> <nicolas.prochazka@gmail.com> wrote:
> > - how many tunnels a peer can manage ?
> > In our environnement, ~ 10 000 clients --> "server"|peer
>
> Each interface can have 65536 peers. Each linux system can have
> multiple interfaces.
>
> (If that peer limit becomes a problem for somebody, it wouldn't be
> difficult to remove it and expand it to 4294967296.)
>
> > how wireguard manage this ( udp tunnel from kernel ? )
>
> Not sure I understand your question. Could you rephrase?
>
> >
> > - about peer key management ?
> > with 10 000 peer keys, how can we manage it
>
> You can load the keys into the interface using wg(8). At some later
> date there may be support for dynamic database stuff.
>
[-- Attachment #2: Type: text/html, Size: 1535 bytes --]
prev parent reply other threads:[~2017-02-17 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 10:12 Nicolas Prochazka
2017-02-17 13:48 ` Jason A. Donenfeld
2017-02-17 13:55 ` Nicolas Prochazka [this message]
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-gZVqKC12_7zaqj1FVsjTe+6A8cuohjqM6fn5_DYRMBQw@mail.gmail.com \
--to=nicolas.prochazka@gmail.com \
--cc=Jason@zx2c4.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).