fix(rust): use legacy netlink ebpf attachment on kernel version 6.6.0+ #8691
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
aya uses newer approach for attaching eBPFs on kernel version 6.6.0+. That attachment approach should be preferable, but currently I notice an unwanted behaviour with it:
TC_ACT_PIPEreturned from the eBPF doesn't pass the packet to the next eBPF, instead it's treated asTC_ACT_OKand moves the packet further the kernel network stack. This makes impossible attaching more that 1 Ockam eBPF at a time, which means only one Ockam node with Privileged Portals can function at a time on a machine.This PR is a hotfix and uses older netlink interface to attach the eBPF even if the kernel supports the newer approach.