feat: client side portion of experimental tunnel

Author: jacobtread

src/api.rs

@@ -95,6 +95,8 @@ struct ServerDetails {
     ident: Option<String>,
     /// Association token if the server supports providing one
     association: Option<String>,
+    /// Tunnel port if the server provides one
+    tunnel_port: Option<u16>,
 }
 
 /// Data from completing a lookup contains the resolved address
@@ -108,6 +110,8 @@ pub struct LookupData {
     pub version: Version,
     /// Association token if the server supports providing one
     pub association: Option<String>,
+    /// Tunnel port if the server provides one
+    pub tunnel_port: Option<u16>,
 }
 
 /// Errors that can occur while looking up a server
@@ -229,6 +233,7 @@ pub async fn lookup_server(
         url,
         version: details.version,
         association: details.association,
+        tunnel_port: details.tunnel_port,
     })
 }
 

src/ctx.rs

@@ -11,4 +11,6 @@ pub struct ClientContext {
     pub base_url: Url,
     /// Optional association token
     pub association: Option<String>,
+    /// Optional tunnel port for tunnel V2 if available
+    pub tunnel_port: Option<u16>,
 }

src/servers/mod.rs

@@ -10,6 +10,7 @@ pub mod qos;
 pub mod redirector;
 pub mod telemetry;
 pub mod tunnel;
+pub mod udp_tunnel;
 
 /// The port the Redirector server will bind to
 pub const REDIRECTOR_PORT: u16 = 42127;