-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ipv6 #10
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
Updated the build system to compile seperate programs for the IPv4 and IPv6 versions of augsburg-traceroute-server. This has following advantages over a single program: + Saving a lot of unnecessary memory overhead A single program would maintain all sessions in a single map, thus forcing the session entries to be large enough to hold IPv6 addresses. By seperating the programs, the IPv4 version doesn't waste any space. + Allowing IPv4 and IPv6 programs to be configured seperately Both the session size and the session timeout can now be configured per-program. Both programs can be attached to a single interface, just run them one after the other.
- Added -4|-6 switch to client to resolve hostnames to the given address family. - Refactored client main function for better code readability. - Added ipv6 support for probe generation.
Moved prev. static functions in headers to internal functions in c file. Cleaned up code to eliminate compile time warnings. Removed duplicate includes in header and source files.
Tests now run inside a virtual machine, which is created and configured by vagrant. The testscript now relies on ipmininet, which provides automatic routing and builtin IPv6 support.
The client defaulted to resolving an IPv4 address for a given hostname if no address family was specified by the user. Now the client tries to resolve an IPv4 address and on failure proceeds to fetch an IPv6 address.
To test the clients merge behaviour the testlab is now configured to create a topology with two unequal-length path and the same igp_metric.
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.
Introduction of IPv6 support for both client and server
Changes to client
-4
and-6
options to resolve a hostname to the specified address family.The option is ignored when a valid IP is specified as the target.
When omitted the client attempts to resolve the target to an IPv4 address, on failure to an IPv6 address.
Server
Testlab