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
Can't delete U32 filters #17
Comments
I found that commenting out the "Handle:" and "U32:" lines in the example above allows the delete to succeed, but obviously that makes it match filters I wasn't intending to delete:
|
Hi! |
Any progress in this issue, I am facing the same issue, while deleting filters System details:
Kernel Version: 5.15.0-051500-generic main.go
Console Output :
|
Thanks for reporting the issue @sanfern As filters of type U32 are different from filters of type BPF, I would appreceate to handle this in a dedicated issue. Did you try to list attached filters with something alone the following lines?
If you compare the reported filters with your initial given input, you will notice differences. In particular pay attention to With regard to the inital request from @ianling: I would be happy to go forward if answers to the questions in #17 (comment) are provided. Otherwise I will in the following months close this issue because of missing response. |
@florianl HI, I have the same issue with Nat action, and the reason is this check. Mirred action have the same check. So for now, we can't just To repoduce, add some filters with NAT action to dummy0:
and run this code:
|
Thanks for reporting. I will try to reproduce it and investigate. |
Filter argument checking was simplified in #120. If you run in further issues, pelase open a new issue. |
If I use
...Filter().Get(...)
to retrieve a filter, I cannot then delete that filter:Filter().Delete(&filter)
From the command line, I am able to add and delete filters as expected:
But I can't figure out how to accomplish the same thing in go-tc.
Do you have any idea how I can delete a filter via go-tc?
The text was updated successfully, but these errors were encountered: