From: Damian Kaczkowski <damian.kaczkowski@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, wireguard@lists.zx2c4.com
Subject: Re: Ability to use one udp port for multiple wg interfaces
Date: Tue, 2 May 2017 11:56:54 +0200 [thread overview]
Message-ID: <CAGzienHd=L8tYn41WdjGSk4hvCWiUW8LUi4C8jf8piBhLA=dng@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pNgSjXeKnzM23Bb3Q=zZJKMDtq-3xevMzdtP7XdoMjkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
Hello Janson.
On 2 May 2017 at 10:55, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> 3. You may have multiple peers on a single wireguard interface. This
> is the configuration that you probably should be using. "It is not
> very friendly to open additional udp ports in multiple peer scenario
> where firewall ACLs are desirable" This is 100% incorrect. With
> multiple peers on an interface and a sufficiently clamped allowed-ips
> entry for each, you'll have perfect firewall ACLs.
>
3. Well if one uses firewall to control flows between zones in environment
with mix protocols (eg. gre, ipsec, openvpn and so on) then using second
tool just to control only wireguard ACLs is not very convenient way from
administrative point of view. Also in case where peer is roaming and
changing its source IP (eg. road warrior) then maintaining wireguard ACLs
will be a huge PITA, if not impossible at large scale.
4. Does wireguard have some means so that iptables can easily
differentiate tunnels (peers) and put them in appropriate 'zone'? like eg.
iptables -m policy --help
iptables -m ah --help
iptables -m esp --help
Or something similar?
Regards.
[-- Attachment #2: Type: text/html, Size: 1776 bytes --]
next prev parent reply other threads:[~2017-05-02 9:48 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 [this message]
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='CAGzienHd=L8tYn41WdjGSk4hvCWiUW8LUi4C8jf8piBhLA=dng@mail.gmail.com' \
--to=damian.kaczkowski@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).