Development discussion of WireGuard
 help / color / mirror / Atom feed
From: wp1065151-spam wp1065151-spam <spam@bcse.de>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Question about ACL
Date: Tue, 9 Mar 2021 13:29:58 +0100 (CET)	[thread overview]
Message-ID: <1806565185.3541.1615292999117@ox.hosteurope.de> (raw)

Hi.


My Question :
I have two peers configured on my WG Server.

Peer A should grant access to Subnet 10.0.10.0/24
Peer B to 10.0.20.0/24.

In Clientconfig i set 
PEER A
AllowedIPs = 10.255.0.0/24,10.0.10.0/24

PEER B
AllowedIPs = 10.255.0.0/24,10.0.20.0/24


SERVER
[Interface]
Address = 10.9.254.1/24
ListenPort = 55555
PrivateKey = AAAAAAAAAAAAAAAAAAAA=

[Peer]
# PEER A
PublicKey = BBBBBBBBBBBBBBBBBBBB=
AllowedIPs = 10.9.254.100/32

[Peer]
# PEER B
PublicKey = CCCCCCCCCCCCCCCCCCC=
AllowedIPs = 10.9.254.101/32


How can i prevent PEER B from changing his config to :
AllowedIPs = 10.255.0.0/24,10.0.20.0/24,10.0.10.0/24
to get access to 10.0.10.0/24 too ?

If i add allowed IP in servers PEER B config, it will add a route for 10.0.10.0/24 to wg0

So PEER A is not longer be able to access this subnet.

How can i set a ACL that allows Peer A and Peer B only to access configured subnet, outside the client config.

I also could be happen that you would like allow your Friend only to access your Server (.101) and Printer (.150) but you Family the whole subnet.
Therefor Friend get in his peer Config:
AllowedIPs = 10.9.254.0/24,10.0.10.101/32,10.0.10.150/32

Family:
AllowedIPs = 10.9.254.0/24,10.0.10.0/24

How we prevent the Friend to change his config to 10.0.10.0/24 ?

                 reply	other threads:[~2021-03-09 21:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1806565185.3541.1615292999117@ox.hosteurope.de \
    --to=spam@bcse.de \
    --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).