From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: wg-quick feature request: excluding the server if it is in AllowedIPs
Date: Thu, 16 Jan 2020 16:57:25 +0500 [thread overview]
Message-ID: <CAN_LGv14Tf8hoJGWDyAXe6sy_1T883Kg44JvGRt9eATqxuH8FA@mail.gmail.com> (raw)
Hello.
Let me explain the use case: we have two networks, x.y.z.0/24 and
172.31.0.0/16, that the staff is supposed to access via a VPN.
However, the VPN server is x.y.z.5 (i.e. in the first network), so
this doesn't work on the client side because of a routing loop:
Endpoint = x.y.z.5:port
AllowedIPs = x.y.z.0/24, 172.31.0.0/16
We had to resort to this:
AllowedIPs = 172.31.0.0/16, x.y.z.128/25, x.y.z.64/26, x.y.z.32/27,
x.y.z.16/28, x.y.z.8/29, x.y.z.0/30, x.y.z.6/31, x.y.z.4/32
Ideally, we should not do this. I believe this is a bug, caused by a
wrong condition in the wg-quick script. Indeed, the special handling
that involves a separate routing table and a firewall mark is
triggered by an attempt to add a default route, while, in my opinion,
it should be triggered by having the VPN server IP covered by one of
the AllowedIPs entries. Could you please fix this?
--
Alexander E. Patrakov
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2020-01-22 19:48 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=CAN_LGv14Tf8hoJGWDyAXe6sy_1T883Kg44JvGRt9eATqxuH8FA@mail.gmail.com \
--to=patrakov@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).