Experiment: Split tunnelling with eBPF #10044
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In my recent travels, I stumbled across the
BPF_PROG_TYPE_CGROUP_SOCK
eBPF program type, which can be attached to control groups to manipulate the sockets that they create, and it takes a mere 4 instructions to set the fwmark on a socket. Doing it this way means that we no longer need NAT and rerouting to perform split tunnelling because we can now do it at socket creation.This is not a serious PR, just yet, but I am thinking this would be a cool building block for a standalone split tunneling daemon that could run independently of the VPN. Or we could migrate the netfilter module into rust now that we no longer need the
xt_cgroups
module.Reference
Inspired by test_cgrp2_sock.c
Checklist