Repository navigation
Conversation
This file contains hidden or 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.
Add a new
dropRateaction parameter. This can be used to specify the probability that subsequent TCP packets in a matched flow are dropped.Example
Behavior
For rates between 1 and 99, once the rule matches, subsequent TCP packets in the flow are independently dropped with the configured probability. A dropped packet uses the packet-level VerdictDrop rather than VerdictDropStream.
Existing full-drop(
block) behavior is preserved for 100% rate.dropRatehas its default value100when not specified.TCP
dropremains a terminal action, consistent withallowandblock: once anallow,block, ordroprule matches a TCP flow, the remaining analyzers for that flow are closed and no later rules are evaluated for that flow.UDP drop behavior is unchanged because it already has separate packet-level semantics, extending it with the same flow-level
dropRatebehavior would change its existing behavior.