-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with Ingress Packets Not Reflecting Changes #950
Comments
I have seen something similar when I was changing checksum of packet during egress using TC egress classifier. I was modifying the checksum of TCP header during egress which was somehow getting over-written by the kernel i believe. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am currently working on a project where I need to remove padding from ingress packets using an ingress classifier. The logs indicate that the packet dimensions are correctly reduced, but it appears that the changes are not propagated to the upper levels.
Upon further investigation, I suspect that the packet is being propagated to the upper levels before the eBPF program completes its execution. I experimented with returning TC_ACT_SHOT at different points in the code, and I noticed that it only takes effect in the first few lines. When placed at the end of the function, it doesn’t work as expected. Could it be an issue related to asynchronicity?
This is the function I'm having problems with:
This is the link to the project.
As I am not an expert in Aya or eBPF, I might be overlooking something crucial. Any insights or suggestions would be greatly appreciated.
The text was updated successfully, but these errors were encountered: