@@ -29,14 +29,10 @@ use super::{
29
29
30
30
/// Constructs a [`MullvadWireguardEndpoint`] with details for how to connect to a Wireguard relay.
31
31
///
32
- /// If entry is `None`, `to_endpoint` configures a single-hop connection using the exit relay data.
33
- /// Otherwise, it constructs a multihop setup using both entry and exit to set up appropriate peer
34
- /// configurations.
35
- ///
36
32
/// # Returns
37
- /// - A configured Mullvad endpoint for Wireguard, encapsulating either a single-hop or multi-hop connection setup .
38
- /// - Returns ` None` if the desired port is not in a valid port range (see
39
- /// [`WireguradRelayQuery ::port`]) or relay addresses cannot be resolved.
33
+ /// - A configured endpoint for Wireguard relay , encapsulating either a single-hop or multi-hop connection.
34
+ /// - Returns [`Option:: None`] if the desired port is not in a valid port range (see
35
+ /// [`WireguardRelayQuery ::port`]) or relay addresses cannot be resolved.
40
36
pub fn wireguard_endpoint (
41
37
query : & WireguardRelayQuery ,
42
38
data : & WireguardEndpointData ,
@@ -97,7 +93,7 @@ fn wireguard_multihop_endpoint(
97
93
let exit = PeerConfig {
98
94
public_key : exit. endpoint_data . unwrap_wireguard_ref ( ) . public_key . clone ( ) ,
99
95
endpoint : exit_endpoint,
100
- // The exit peer should be able to route incomming VPN traffic to the rest of
96
+ // The exit peer should be able to route incoming VPN traffic to the rest of
101
97
// the internet.
102
98
allowed_ips : all_of_the_internet ( ) ,
103
99
// This will be filled in later, not the relay selector's problem
0 commit comments