diff options
author | 2019-01-08 01:51:12 +0100 | |
---|---|---|
committer | 2019-01-08 01:51:12 +0100 | |
commit | 49f287439e85770cd9d80ae4fe8902f3f9e61acc (patch) | |
tree | b501f2bb8759d9771d4c105d38117c754e7a5a20 /WireGuard | |
parent | Avoid dynamic MTU calculations for now (diff) | |
download | wireguard-apple-49f287439e85770cd9d80ae4fe8902f3f9e61acc.tar.xz wireguard-apple-49f287439e85770cd9d80ae4fe8902f3f9e61acc.zip |
PacketTunnelSettingsGenerator: use 127.0.0.1 as dummy address
It turns out that using 0.0.0.0 somehow conflicts with DNS lookups when
CLAT is in use.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Diffstat (limited to 'WireGuard')
-rw-r--r-- | WireGuard/WireGuardNetworkExtension/PacketTunnelSettingsGenerator.swift | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/WireGuard/WireGuardNetworkExtension/PacketTunnelSettingsGenerator.swift b/WireGuard/WireGuardNetworkExtension/PacketTunnelSettingsGenerator.swift index b011c2a..f6eb722 100644 --- a/WireGuard/WireGuardNetworkExtension/PacketTunnelSettingsGenerator.swift +++ b/WireGuard/WireGuardNetworkExtension/PacketTunnelSettingsGenerator.swift @@ -63,9 +63,7 @@ class PacketTunnelSettingsGenerator { * make sense. So, we fill it in with this placeholder, which is not * a valid IP address that will actually route over the Internet. */ - let remoteAddress = "0.0.0.0" - - let networkSettings = NEPacketTunnelNetworkSettings(tunnelRemoteAddress: remoteAddress) + let networkSettings = NEPacketTunnelNetworkSettings(tunnelRemoteAddress: "127.0.0.1") let dnsServerStrings = tunnelConfiguration.interface.dns.map { $0.stringRepresentation } let dnsSettings = NEDNSSettings(servers: dnsServerStrings) |