client: Implement IPv6

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 <[email protected]>
wlanslovenija · Jan 13, 2020 · afe661d · afe661d
1 parent 21ddfdc
commit afe661d
Show file tree

Hide file tree

Showing 2 changed files with 122 additions and 72 deletions.
diff --git a/HISTORY.rst b/HISTORY.rst
@@ -8,6 +8,7 @@ vNEXT
   This can be achieved by deleting the old virtualenv folder and recreating it.
   For recreating the virtualenv you can refer to the "Installation" section of
   the broker `installation chapter in the Tunneldigger documentation`_.
+* IPv6 support for both client and broker.
 * Fixed compatibility with new Linux kernels on the broker side: New kernels
   force the l2tpv3 session ID to be unique system-wide, while old tunneldigger
   clients have a hard-coded ID of 1 for both ends of the tunnel. When a new