All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bzzzz <lazyvirus@gmx.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Many users
Date: Sun, 6 Aug 2017 23:10:21 +0200	[thread overview]
Message-ID: <20170806231021.3482e97c@msi.defcon1> (raw)
In-Reply-To: <20170806205739.GA3134@zx2c4.com>

On Sun, 6 Aug 2017 22:57:42 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:

> On Sun, Aug 06, 2017 at 10:34:12PM +0200, Bzzzz wrote:
> > I guess, when you're talking about "thousands of interfaces", you
> > mean virtual ones ? Do you recall how many machines he was using ?  
> 
> On the same machine, I mean.

Now I'm sure.

> I guess you could simulate this kind of thing with:
> 
> printf '[Interface]\nPrivateKey=%s\n' "$(wg genkey)" > conf
> head -c $(( 33 * 10000 )) /dev/urandom | base64 | tr -d '\n' | fold -b
> -w 44 | sed -n 's/\(.*\)../[Peer]\nPublicKey=\1A=/p' >> conf for i in
> {1..10000}; do ip link add wg$i type wireguard; wg setconf
> wg$i ./conf; done

Nice piece of code.

> Careful, though!
> 
> > 
> > BTW, for such cases may be it could be interesting to link WG to a
> > sqlite DB ?  
> 
> I've actually got something for this coming through the pipeline soon.
> I'll keep the list posted when it's ready.

Now, THIS will be a very nice thing - and so much better when
adding|removing a user than a huge configuration file.

As there's no real hurry, I'll wait for this feature to appear.

Thanks for your answers.

JY

  reply	other threads:[~2017-08-06 20:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-06 19:02 Many users Bzzzz
2017-08-06 20:22 ` Jason A. Donenfeld
2017-08-06 20:34   ` Bzzzz
2017-08-06 20:57     ` Jason A. Donenfeld
2017-08-06 21:10       ` Bzzzz [this message]
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=20170806231021.3482e97c@msi.defcon1 \
    --to=lazyvirus@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.