Repository navigation
fix(classify): reserve likely for measured filtering - #37
Merged
Merged
Conversation
Untested filtering read stronger than measured strict filtering, so one router improved by being measured less.
An IPv6 verdict could sit in front of a symmetric IPv4 NAT with nothing in the output to say so.
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.
Untested filtering read stronger than measured strict filtering, so one router improved by being measured less;
likelynow requires measured endpoint-independent filtering. A newipv4_untestedwarning says when a verdict covers IPv6 only. Comments also drop line-number references to the design doc.