Hello Janson. On 2 May 2017 at 10:55, Jason A. Donenfeld <[email protected]> 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.
_______________________________________________ WireGuard mailing list [email protected] https://lists.zx2c4.com/mailman/listinfo/wireguard
