Implementation of router alert handling #10
Merged
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
added 5 commits
January 25, 2013 16:48
enable correct function with IPv6 auto-configured networks
- changed: IPv6TrafGen configuration options for router alert support
|
Hi Marcus, thank you for this patch! For the time being (we are working on other topics right now) I put your commits into the topic/router-alert-handling branch. Please allow us a little time to review and integrate them into master. |
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.
This set of commits implements the handling of router alert headers for IPv4 and IPv6. It also fixes a bug in IPvXTrafGen which prevented it from working in a non-flat IPv6 network. The router alert handling implementation allows protocol developers to intercept packets at each intermediate node in a network e.g. to implement new QoS signalling protocols, while still being able to reuse the standard Router and Host modules. The implementation is somewhat preliminary in a sense, that it does not fix the issues with the option header handling in IPv4. It still uses only one option header there.