From: Chris Osicki <wg@osk.ch>
To: Roman Mamedov <rm@romanrm.net>
Cc: Gijs Conijn <egc112@outlook.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WG default routing
Date: Tue, 5 Jan 2021 22:13:01 +0100 [thread overview]
Message-ID: <20210105211301.GC31054@server> (raw)
In-Reply-To: <20210106012530.2754726a@natsu>
On Wed, Jan 06, 2021 at 01:25:30AM +0500, Roman Mamedov wrote:
> On Tue, 5 Jan 2021 21:12:12 +0100
> Chris Osicki <wg@osk.ch> wrote:
>
> > As far as I can see after few tests, AllowedIPs config file option has nothing to do with routing and I hope
> > it will stay like this.
>
> wg-quick uses AllowedIPs to also set up matching entries in the system routing
> table. This can be disabled in its config.
>
> > It is just a filter
>
> It is not only a filter on incoming packets, but also WG's internal routing
> table for knowing which packets should be sent to which peer.
I'm sorry to contradict you but after some more readig I have to :-)
WG has no "internal routing table", wg-quick (which, BTW, is not the subject of my query) uses it to modify
kernel routing tables, from the wg-quick man page:
It infers all routes from the list of peers' allowed IPs, and automatically adds them to the system routing
table. If one of those routes is the default route (0.0.0.0/0 or ::/0), then it uses ip-rule(8) to handle
overriding of the default gateway.
So, in my test config I have a server, 10.10.10.1 and two clients, 10.10.10.2/3
If on the server I remove the AllowedIPs option, no one can connect.
Giving AllowedIPs = 10.10.10.0/24 both clients can connect and routing in them stays as it was.
The same for the clients, without AllowedIPs = 10.10.10.0/24 cannot connect.
Thus, my question still remains: why this filtering function?
>
> --
> With respect,
> Roman
Regards,
Chris
next prev parent reply other threads:[~2021-01-05 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 21:54 Chris Osicki
2021-01-04 13:22 ` Gijs Conijn
2021-01-05 20:12 ` Chris Osicki
2021-01-05 20:25 ` Roman Mamedov
2021-01-05 21:13 ` Chris Osicki [this message]
2021-01-05 23:50 ` Phillip McMahon
2021-01-06 1:03 ` Corey Costello
2021-01-06 1:17 ` Samuel Holland
2021-01-04 13:38 ` Henning Reich
2021-01-05 20:15 ` Chris Osicki
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=20210105211301.GC31054@server \
--to=wg@osk.ch \
--cc=egc112@outlook.com \
--cc=rm@romanrm.net \
--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).