From: Feng Li <lifeng1519@gmail.com>
To: Chris <wireguard@spam-free.eu>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Enhance the "AllowedIPs"
Date: Wed, 17 Mar 2021 13:30:58 +0800 [thread overview]
Message-ID: <CAEK8JBBpJRo1ShMGJfSRU8OASEDd+LRFWLp0GFRkR7=ruPz1yQ@mail.gmail.com> (raw)
In-Reply-To: <b7fb35f2-5d82-b4d6-5add-e18f5d032010@spam-free.eu>
Thanks.
Add a route is simple on Linux, But it's not simple for other
platforms, like Windows.
So changes the AllowedIPs is the best option.
On Tue, Mar 16, 2021 at 7:40 PM Chris <wireguard@spam-free.eu> wrote:
>
> Just in case:
> I guess you have already thought about using the post script to add a separate
> route to 192.160.0.0/16 using the original path with a lower metric.
>
> On 15/03/2021 08:57, Feng Li wrote:
> > Hi,
> >
> > As we know, the AllowedIPs will set the route table. However, if we
> > want to set the CIDR, but except for some CIDR range, it's not so easy
> > and out of the box. For example, if I want to route my all traffic,
> > except the 192.168.0.0/16. I have to calculate the two CIDR
> > difference:
> >
> > AllowedIPs =
> > 0.0.0.0/1 + 128.0.0.0/1 - 192.168.0.0/16
> > =
> > 0.0.0.0/5,8.0.0.0/7,11.0.0.0/8,12.0.0.0/6,16.0.0.0/4,32.0.0.0/3,64.0.0.0/2,128.0.0.0/2,192.0.0.0/9,192.128.0.0/11,192.160.0.0/13,192.169.0.0/16,192.170.0.0/15,192.172.0.0/14,192.176.0.0/12,192.192.0.0/10,193.0.0.0/8,194.0.0.0/7,196.0.0.0/6,200.0.0.0/5,208.0.0.0/4,224.0.0.0/3,10.99.0.0/24
> >
> > Is it possible to be built in Wireguard in the future? I think it's very useful.
> >
> > The discussion link is here:
> > https://www.reddit.com/r/WireGuard/comments/m44fi5/enhance_the_allowedips/
> >
> > Thanks.
>
prev parent reply other threads:[~2021-03-17 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 7:57 Enhance the "AllowedIPs" Feng Li
2021-03-15 13:31 ` Lonnie Abelbeck
2021-03-15 14:57 ` Aaron Jones
2021-03-16 11:33 ` Chris
2021-03-17 5:30 ` Feng Li [this message]
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='CAEK8JBBpJRo1ShMGJfSRU8OASEDd+LRFWLp0GFRkR7=ruPz1yQ@mail.gmail.com' \
--to=lifeng1519@gmail.com \
--cc=wireguard@lists.zx2c4.com \
--cc=wireguard@spam-free.eu \
/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).