Arch Linux

Ok, we can add it as make dependency, but that's just half of the game.
Does all this (or libbpf?) become a hard dependency then? Or can we list it as optional dependency?

Or is nothing required at runtime? I do not think so.
At least I could not find anything linking against libbpf...

sorry for late reply

libbpf is an optional dependency (dlopen in libsystemd-shared-250.so, like libfido2 or qrencode)

Are there any plans on building systemd with bpf? Service-level network interface restriction is a really nice feature.

I am not against this, but have not worked through all the details.
Besides libbpf this requires dependencies at runtime (clang? llvm?) that should be listed in `optdepends`, no?

From the systemd 252 NEWS file:

Experimental features:
* BPF programs can now be compiled with bpf-gcc (requires libbpf >= 1.0
and bpftool >= 7.0).

Would bpf-gcc be an alternative? Although Arch's GCC package does not seem to enable BPF support at all, currently.

Note to self... How to test this:

systemd-run -t -p RestrictNetworkInterfaces="lo" ping archlinux.org

This should fail if bpf is functional.

Please test systemd 252.2-4...

It works flawlessly here. Thanks!