From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [PATCH wireguard-tools v3 0/3] ipc: linux: kernel-side netdevice filtering
Date: Thu, 12 Mar 2026 00:02:52 +0100 [thread overview]
Message-ID: <abH0nBlQmggFAFt7@zx2c4.com> (raw)
In-Reply-To: <20260130191058.5123-1-ast@fiberby.net>
On Fri, Jan 30, 2026 at 07:10:52PM +0000, Asbjørn Sloth Tønnesen wrote:
> Move device filtering to the kernel, thereby reducing netlink traffic.
>
> The first patch request kernel-side filtering.
>
> The second patch requests that the kernel doesn't include statistics
> in netdevice dumps.
>
> The third patch removes the old filtering code, as an
> additional step, which breaks on earlier than Linux v4.6.
>
> I assume that a dependency on Linux v4.6+ is acceptable for wg-tools
> now, as wireguard-linux-compat haven't been updated for 3 years.
Interesting series. If I'm going to apply this, I'm going to apply it,
and so the ifdefs you've added won't matter much; this will still break
wireguard-linux-compat. But maybe it's time to do so. So if you're up
for sending a v4, just do it like there's no yesterday.
Also, does this filtering need to also be added to the embeddable c
library contrib code?
Thanks for this patch. I'll start thinking seriously about
wireguard-linux-compat sunsetting.
Jason
prev parent reply other threads:[~2026-03-11 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 19:10 [PATCH wireguard-tools v3 0/3] ipc: linux: kernel-side netdevice filtering Asbjørn Sloth Tønnesen
2026-01-30 19:10 ` [PATCH wireguard-tools v3 1/3] ipc: linux: filter netdevices kernel-side Asbjørn Sloth Tønnesen
2026-01-30 19:10 ` [PATCH wireguard-tools v3 2/3] ipc: linux: skip statistics on netdevice listing Asbjørn Sloth Tønnesen
2026-01-30 19:10 ` [PATCH wireguard-tools v3 3/3] ipc: linux: remove user-space netdevice filtering Asbjørn Sloth Tønnesen
2026-03-11 23:02 ` Jason A. Donenfeld [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=abH0nBlQmggFAFt7@zx2c4.com \
--to=jason@zx2c4.com \
--cc=ast@fiberby.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