Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Damian Kaczkowski <damian.kaczkowski@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Ability to use one udp port for multiple wg interfaces
Date: Tue, 2 May 2017 10:20:46 +0200	[thread overview]
Message-ID: <CAGzienFDihyN8fDbKj4KQ-1cwz53_u7Vz3G37P08+wS=hbF0LA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

Hello.

I'm trying to run two wg interfaces bound to one udp port. eg. wg0 ang wg1
on 51820/udp . wg shows that both interfaces are created (wg0 and wg1). wg
also shows that all peers on both interfaces are defined. However only
peers defined on one wg interface (either wg0 or wg1) are able to establish
connection. Peers on the other interface are not able to connect.

Is this currently unsupported configuration?

Or is this supported configuration and I am doing something wrong?

If unsupported, do you consider to support it in the future?

It would be useful if one wants to easily manage ACLs via firewall rules
defined by wg interfaces (easy to define zones), but do not want to open
multiple ports for every new zone/peer(s). Currently one have to open one
udp port per wg interface. It is not very friendly to open additional udp
ports in multiple peer scenario where firewall ACLs are desirable. If one
have limited number of free udp ports then it also does not scale well.

I am using wireguard build no 20170115 on lede/mips linux.

Greets.

[-- Attachment #2: Type: text/html, Size: 1256 bytes --]

             reply	other threads:[~2017-05-02  8:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  8:20 Damian Kaczkowski [this message]
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

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='CAGzienFDihyN8fDbKj4KQ-1cwz53_u7Vz3G37P08+wS=hbF0LA@mail.gmail.com' \
    --to=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).