use iptables to classify packets (#1031) #1038
Merged
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.
cherry-pick #1031 to release-1.0
Signed-off-by: Yang Keao keao.yang@yahoo.com
What problem does this PR solve?
#688 The default kernel of GKE is not built with
CONFIG_NET_EMATCH
andCONFIG_NET_EMATCH_IPSET
so we cannot match ipset as a filter in tc.This PR uses
iptables -A TC-TABLES-0 -m set --match-set A dst -j CLASSIFY --set-class 3:4 -w 5
to replace it.What is changed and how does it work?
Checklist
Tests
I have run the e2e test on GKE, and it works well.