From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Vasili Pupkin <diggest@gmail.com>
Cc: "jwollrath@web.de" <jwollrath@web.de>,
"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] wg-quick: linux: add support for nft and prefer it
Date: Tue, 10 Dec 2019 23:09:14 +0100 [thread overview]
Message-ID: <CAHmME9pSsTogYKMObNuy20FCRE8tNrjT9OVefn1GqqmG1B7q6w@mail.gmail.com> (raw)
In-Reply-To: <a8f51c8e-d0e8-aaa6-024f-70b65007559f@gmail.com>
On Tue, Dec 10, 2019 at 11:03 PM Vasili Pupkin <diggest@gmail.com> wrote:
> As far as I know both of them are maintained in the same repository and
> both use the same userspace library to interact with the kernel and down
> there all the rules are translated into BPF code which in turn is
> compiled into machine code by kernel BPF JIT compiler.
"bpfilter" is a WIP, but that's not today how iptables or nftables
work, at all. I'm not sure your statement about userspace is entirely
correct either.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-12-10 22:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 15:48 Jason A. Donenfeld
2019-12-10 16:52 ` Jordan Glover
2019-12-10 16:54 ` Jason A. Donenfeld
2019-12-10 17:05 ` Jordan Glover
2019-12-10 17:11 ` Jason A. Donenfeld
2019-12-10 17:12 ` Roman Mamedov
2019-12-10 17:28 ` Davide Depau
2019-12-10 17:33 ` Matthias Urlichs
2019-12-10 17:36 ` Jason A. Donenfeld
2019-12-10 18:00 ` Roman Mamedov
2019-12-10 18:58 ` Jordan Glover
2019-12-10 19:15 ` Jason A. Donenfeld
2019-12-10 20:30 ` Jordan Glover
2019-12-10 20:34 ` Jason A. Donenfeld
2019-12-10 21:56 ` Vasili Pupkin
2019-12-10 22:09 ` Jason A. Donenfeld [this message]
2019-12-10 22:27 ` Vasili Pupkin
2019-12-12 11:21 ` Jason A. Donenfeld
2019-12-10 17:31 ` Vasili Pupkin
2019-12-10 17:38 ` Jason A. Donenfeld
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=CAHmME9pSsTogYKMObNuy20FCRE8tNrjT9OVefn1GqqmG1B7q6w@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=diggest@gmail.com \
--cc=jwollrath@web.de \
--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).