Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Damian Kaczkowski <damian.kaczkowski@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Ability to use one udp port for multiple wg interfaces
Date: Thu, 11 May 2017 12:30:46 +0200	[thread overview]
Message-ID: <CAHmME9ow+VEY+aU1_NXEsivLpEZQ-BAfdWxEpLv0SOpMsOwp1g@mail.gmail.com> (raw)
In-Reply-To: <CAGzienGzypKvYQZBShJuZp9kZHhj26Rc8-qtObD+Ap_+XhB4+w@mail.gmail.com>

On Fri, May 5, 2017 at 8:28 PM, Damian Kaczkowski
<damian.kaczkowski@gmail.com> wrote:
> True. But I still think that ability to assign multi interfaces to one udp
> port would be handy. Eg when one want to use only specific and limited ports
> (like eg 53) for wireguard but still wants to have more interfaces at one's
> disposal. Possible use case - be able to easily assign and group various
> peers to different interfaces and monitor those interfaces parameters
> (exposed eg by kernel) using monitoring tools capable of collecting various
> information/data and/or plotting graphs like bandwidth, traffic, and so on.
> This info could be later used for analysing or debugging.

No, you're doing it wrong. Those monitoring use cases you mentioned
are already taken care of by the existing design. If you need help
with a particular configuration or setup, you're free to ask about
those particular use cases. But what you've asked so far simply isn't
the WireGuard way of doing things; we offer here a better design than
that.


> Reading through the docs.
>
> I come to scenario where I would like to disable whole allowed-ips thing.

Then either you're doing things horribly wrong, or WireGuard isn't the
tool for you. AllowedIPs is the essential concept.

If you have questions about how to reach a particular goal, we can
help you. But I believe this particular conversation has reached a
dead end.

      reply	other threads:[~2017-05-11 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  8:20 Damian Kaczkowski
2017-05-02  8:55 ` Jason A. Donenfeld
2017-05-02  9:56   ` Damian Kaczkowski
2017-05-02 16:32     ` Jason A. Donenfeld
2017-05-02 17:59       ` Damian Kaczkowski
2017-05-02 19:45         ` Jason A. Donenfeld
2017-05-05 18:28           ` Damian Kaczkowski
2017-05-11 10:30             ` Jason A. Donenfeld [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=CAHmME9ow+VEY+aU1_NXEsivLpEZQ-BAfdWxEpLv0SOpMsOwp1g@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=damian.kaczkowski@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).