-
Notifications
You must be signed in to change notification settings - Fork 209
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
test: Try flow matching from progressive offsets in case of failures
Retry flow matching again if all flow requirements can not be met. Start the new round from the flow following the previous first match. This effectively retries flow matching from different L4 connections, as the ephemeral source port found from the first match is fixed for the remaining requirements. By skipping the previous first match the match can succeed on a different L4 connection. Merge flow validation results for each flow requirement before returning. Without this flow validation was reported successful when at least one flow validation requirement was met, hiding failures in later requirements. For example, if successful DNS reply from proxy is required, it may be on a different UDP or TCP port than the first DNS resolution exchange that may have failed. This capability was inadvertently removed in #319. Fixes: #319 Signed-off-by: Jarno Rajahalme <[email protected]>
- Loading branch information
1 parent
b764b09
commit 088eb3f
Showing
1 changed file
with
47 additions
and
41 deletions.
There are no files selected for viewing
This file contains 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