Wrong range Assumption #5
Open
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
Test IP address from Telecom Argentina S.A. expected wrong data. LACNIC answers in shortened CIDR form 190.190/15 which in fact is 190.190.0.0/15 and not the wronly assumed 190.0.0.190/15 (which does not include the input parameter IP). Wrong assumption due to seemingly wrong implementation by the framework to analyze 190.190/15 correctly. The expected false results were only met because in fact the method by which the AddressRange is analyzed returns false data.
Whacky LACNIC CIDR response correction: 190.190/15 -> 190.190.0.0/15
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.
Test IP address from Telecom Argentina S.A. expected wrong data.
LACNIC answers in shortened CIDR form 190.190/15 which in fact is 190.190.0.0/15 and not the wronly assumed 190.0.0.190/15 (which does not include the input parameter IP).
Wrong assumption due to seemingly wrong implementation by the framework to analyze 190.190/15 correctly. The expected false results were only met because in fact the method by which the AddressRange is analyzed returns false data.