Initial IPv6 support #116
Closed
Initial IPv6 support #116
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
Merged
kaechele
force-pushed
the
ipv6
branch
3 times, most recently
from
edb1637
to
afe661d
Compare
Add a link to useful information on this particular error which is most likely triggered by a bug in the Kernel. This should give users a way to identify if they are affected and give them hints on how to rectify the situation. Signed-off-by: Felix Kaechele <felix@kaechele.ca>
This reverts commit a461a11.
Also allow listening on multiple addresses to enable Dual Stack operation. Signed-off-by: Felix Kaechele <felix@kaechele.ca>
This adds IPv6 capabilities to the client. A fallback to IPv4 has been implemented for DNS names that return both an A and AAAA record but where the broker only replies to IPv4 requests. This removes binding to local IPs or interfaces as we connect() the socket which makes the Kernel choose the local endpoint automatically based on the interface that was used for the outgoing request. IPv6 Addresses can be passed to the client using the -b parameter like this: tunneldigger [opts] -b [2001:db8::1]:8942 you can also specify the interface scope for IPv6 like this: tunneldigger [opts] -b [fe80::1%ens3]:8942 Signed-off-by: Felix Kaechele <felix@kaechele.ca>
|
I will rework and resubmit this. This doesn't cleanly rebase or merge onto master by now anyway. |
|
@kaechele great! Indeed I think we can consider the other patches this is based on to be "battle-tested" by now and hence can move forward. I wonder if we should have a release of some sort... |
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 implements IPv6 support for both broker and client.
The broker implementation is very straightforward.
The client is a little more involved.
Initial testing showed mixed results. My initial testing suggests there may be an MTU issue with a particular ISP in our region when using IPv6. So further testing would be appreciated.
Depends on #115 and #110
Fixes #75