Merge pull request #199 from telepresenceio/thallgren/broken-vpn-links

Fix broken links in VPN reference page.
telepresenceio · Dec 8, 2023 · d5f292d · d5f292d
2 parents 8c53743 + 32d0382
commit d5f292d
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/v2.5/reference/vpn.md b/docs/v2.5/reference/vpn.md
@@ -21,12 +21,12 @@ You may need to configure this on both the client and server sides.
 Client-side, taking the Tunnelblick client as an example, you must ensure that
 the `Route all IPv4 traffic through the VPN` tickbox is not enabled:
 
-<img src="../../images/tunnelblick.png" />
+<img src="../images/tunnelblick.png" />
 
 Server-side, taking AWS' ClientVPN as an example, you simply have to enable
 split-tunnel mode:
 
-<img src="../../images/split-tunnel.png" />
+<img src="../images/split-tunnel.png" />
 
 In AWS, this setting can be toggled without reprovisioning the VPN. Other cloud providers may work differently.
 
@@ -111,7 +111,7 @@ hosts from being masked.
 This might be particularly important for DNS resolution. In an AWS ClientVPN VPN it is often
 customary to set the `.2` host as a DNS server (e.g. `10.0.0.2` in this case):
 
-<img src="../../images/vpn-dns.png" />
+<img src="../images/vpn-dns.png" />
 
 If this is the case for your VPN, you should place the DNS server in the never-proxy list for your
 cluster. In your kubeconfig file, add a `telepresence` extension like so: