Feature/pmtu discovery #64
Open
Conversation
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
- only discover pmtu for reachable hosts - pick a starting test point closer to the more probable MTU - tune the interval and timeout based on discovered RTT
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.
Here is a potential implementation of path MTU discovery. It has recently been mentioned in issue #54 and #71
Some test results here:
https://github.com/acooks/icmplib/wiki
The results show that interfaces conform to the Robustness principle in that they may accept packets somewhat larger than the configured MTU, but won't send anything larger than the configured MTU.
Characterizing that asymmetric behavior was what motivated me to implement the pmtu discovery.