Development discussion of WireGuard
 help / color / mirror / Atom feed
From: nicolas prochazka <prochazka.nicolas@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [wireguard-dev] Ability to use one udp port for multiple wg interfaces
Date: Thu, 21 Sep 2017 13:46:10 +0200	[thread overview]
Message-ID: <CADdae-jaxO+P-fcqgqjDRWkih4YhxS__A=weDtHVhB3j4R6W_A@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oMQ+3yUA8Da-m8YAkNgJ-aJ3uRuhp-uHJq_mRQ1hJDDQ@mail.gmail.com>

Hello,
i known, but we are using one interface by customer, each interface
manages multiple peers ( > 500 )
as
wg_interface0 = client 0  = 500 peers
wf_interfacen= client n = 500 peers

at this moment, only one interface wg0  manage all peers and all
customers , it's very complicating for the administrive tasks , qos,
client separation ....

Regards,
NIcolas

2017-09-21 13:25 GMT+02:00 Jason A. Donenfeld <Jason@zx2c4.com>:
> I'd recommend you use multiple peers per interface. The strong binding
> with allowed-ips enables you to use qos, network analysis, security,
> and iptables rules in a very straightforward way.

  reply	other threads:[~2017-09-21 11:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21  9:32 nicolas prochazka
2017-09-21 11:25 ` Jason A. Donenfeld
2017-09-21 11:46   ` nicolas prochazka [this message]
2017-09-21 11:54     ` Jason A. Donenfeld
2017-09-21 11:55 ` Jason A. Donenfeld
2017-09-21 12:17   ` nicolas prochazka
2017-09-21 12:54     ` Jason A. Donenfeld
2017-09-21 13:14       ` nicolas prochazka
2017-09-21 13:24         ` Jason A. Donenfeld
2017-09-21 15:29           ` nicolas prochazka
2017-09-21 15:36             ` Jason A. Donenfeld

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-jaxO+P-fcqgqjDRWkih4YhxS__A=weDtHVhB3j4R6W_A@mail.gmail.com' \
    --to=prochazka.nicolas@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).