-
Notifications
You must be signed in to change notification settings - Fork 45
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
Adding flower rule results in unexpected output in tc -s filter show
#19
Comments
Hi @dennisafa Can you confirm it got fixed? |
Thanks so much for getting to this so quickly! I will test it today. |
Awesome, I'm getting the correct flow rule output now:
In addition to this - I am trying to add actions that are applied on a match of this rule. My end goal is to have a flow rule that looks like this:
My current code is to construct an actions array and add that to the Matchall object, then add that to the qdisc using Chain().Add(). However, I get an "operation not supported" error. Here is my code:
Error: |
Update - I managed to figure out how to add actions to a flower rule. I edited flower.go to use the tcaFlowerAct index, and added marshalling/unmarshalling logic. I'll open a PR for this so that others may use it. |
Hello! I'm adding a flower rule to a qdisc like so:
I expect to see a tc flower rule that matches on destination port ID of 1. Instead, I get this:
The outcome in the flow rules is always dst_port * 256. Perhaps there is a bug in marshalling the data?
The text was updated successfully, but these errors were encountered: