From: "Daniel Gröber" <dxld@darkboxed.org>
To: Alexander Zubkov <green@qrator.net>
Cc: Maria Matejka <maria.matejka@nic.cz>,
Juliusz Chroboczek <jch@irif.fr>, Kyle Rose <krose@krose.org>,
bird-users@network.cz, babel-users@alioth-lists.debian.net,
wireguard@lists.zx2c4.com
Subject: Re: [Babel-users] [RFC] Replace WireGuard AllowedIPs with IP route attribute
Date: Sat, 18 Nov 2023 03:19:01 +0100 [thread overview]
Message-ID: <20231118021901.47kzvwn4pup4vkmg@House.clients.dxld.at> (raw)
In-Reply-To: <CABr+u0YVm+rCDybpaJQdXW4GuRbOnRgELG33pWPAgOSrwc-YbA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Hi Alexander,
On Thu, Nov 09, 2023 at 12:57:26PM +0100, Alexander Zubkov wrote:
> I heard recently about the lightweight tunnel infrastructure in Linux
> kernel (ip route ... encap ...). And I think this might be helpful in
> the context of this thread.
I hadn't seen that yet, thanks for pointing it out.
> Linux kernel allows already to add encapsulation parameters to the route
> entry in its table. So you do not need to create tunnel devices for
> that. And wireguard encapsulation and destination might be added there
> too.
Right, I think ultimately it's going to come down to either technical
constraints or in the absence of that, maintainer preference whether
via-wgpeer or "encap wg" is the way. The idea is very similar anyway.
> But as I understood the technology, it works only in one way (for
> outgoing packets) and the decapsulation should be processed separately,
> for example in case of VXLAN and MPLS they have their own tables.
That would be a problem as I specifically want to tie the source address
filtering to this too. I'll have a look at the internals (if and) when I
get around to starting work on this.
Thanks,
--Daniel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-18 2:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 14:02 Daniel Gröber
[not found] ` <5112ea1f-0f67-4907-a3c5-b6c7b9e591ca@kr217.de>
2023-08-19 18:17 ` Daniel Gröber
2023-08-19 20:00 ` [Babel-users] " Steffen Vogel
2023-08-19 21:23 ` Daniel Gröber
2023-08-28 15:40 ` Kyle Rose
2023-08-28 16:07 ` Daniel Gröber
2023-08-28 17:40 ` Juliusz Chroboczek
2023-08-28 17:55 ` Kyle Rose
2023-08-28 22:13 ` Daniel Gröber
2023-09-03 3:21 ` Ivan Labáth
2023-09-29 13:12 ` Daniel Gröber
2023-09-29 16:19 ` Reto
[not found] ` <804a0c0a-78df-7f4c-1d0d-213e8bdb4120@nic.cz>
2023-11-09 11:57 ` [Babel-users] " Alexander Zubkov
2023-11-18 2:19 ` Daniel Gröber [this message]
[not found] ` <918e1d5b-9f11-4f9c-bf9a-94cb0d41ce2b@app.fastmail.com>
2023-11-18 12:22 ` Juliusz Chroboczek
2023-11-20 2:05 ` Daniel Gröber
[not found] ` <CABr+u0b6vrZoYzQcMiCXX7W0XsQRNMzQfZnT5cK1MQoZ4NoqkA@mail.gmail.com>
2023-11-22 7:39 ` Daniel Gröber
2023-08-19 20:05 ` Kyle Rose
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=20231118021901.47kzvwn4pup4vkmg@House.clients.dxld.at \
--to=dxld@darkboxed.org \
--cc=babel-users@alioth-lists.debian.net \
--cc=bird-users@network.cz \
--cc=green@qrator.net \
--cc=jch@irif.fr \
--cc=krose@krose.org \
--cc=maria.matejka@nic.cz \
--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).