summaryrefslogtreecommitdiff
path: root/_posts/2023-07-02-shoot-foot-wireguard.md
diff options
context:
space:
mode:
authoruvok cheetah2024-10-06 12:27:27 +0200
committeruvok cheetah2024-10-06 12:27:27 +0200
commitcffed9b2a703bda44174f4b47020ed7fedfcc1f1 (patch)
treed754c0ec2df7139696f476c21f6b1becb86f8e6a /_posts/2023-07-02-shoot-foot-wireguard.md
parent54e88b8d8a2fcf3db198b7c3c37844c3072b1e07 (diff)
Update image tag use
Diffstat (limited to '_posts/2023-07-02-shoot-foot-wireguard.md')
-rw-r--r--_posts/2023-07-02-shoot-foot-wireguard.md32
1 files changed, 20 insertions, 12 deletions
diff --git a/_posts/2023-07-02-shoot-foot-wireguard.md b/_posts/2023-07-02-shoot-foot-wireguard.md
index 3a096f1..41fda9a 100644
--- a/_posts/2023-07-02-shoot-foot-wireguard.md
+++ b/_posts/2023-07-02-shoot-foot-wireguard.md
@@ -17,9 +17,11 @@ to update again? Now that I think about it, I can't remember I actually I ever
tested the connection. I tested the connection once when my OpenWRT router was still
running in a VM. Maybe I forgot to set up some things?
-<a href="https://pics.uvokchee.de/upload/2023/07/02/20230702201107-0ecdfc52.png"><img
- src="https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702201107-0ecdfc52-sm.png"
- alt="A diagram showing the network components of my Wireguard setup." /></a>
+{% linked_image
+ url="https://pics.uvokchee.de/upload/2023/07/02/20230702201107-0ecdfc52.png"
+ img="https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702201107-0ecdfc52-sm.png"
+ alt="A diagram showing the network components of my Wireguard setup."
+%}
But hey, no worries, I'll simply connect to my VPS, and let the Wireguard
routing do its job. Just move the `AllowedIP=0.0.0.0/24`
@@ -35,9 +37,11 @@ to try to figure out what went wrong.
Well, lets see, what are the AllowedIPs...
-<a href="https://pics.uvokchee.de/upload/2023/07/02/20230702201107-5df12e17.png"><img
- src="https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702201107-5df12e17-sm.png"
- alt="Same diagram as before. Added: AllowedIPs." /></a>
+{% linked_image
+ url="https://pics.uvokchee.de/upload/2023/07/02/20230702201107-5df12e17.png"
+ img="https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702201107-5df12e17-sm.png"
+ alt="Same diagram as before. Added: AllowedIPs."
+%}
Hm. Seems good enough.
The smartphone pings to the VPS get answered all right. The AllowedIPs match there.
@@ -56,9 +60,11 @@ ping from Smartphone to OpenWRT... Still stuck. The heck?
Okay, let's see the configs again. Very carefully.
-<a href="https://pics.uvokchee.de/upload/2023/07/02/20230702201107-597a7b3d.png"><img
- src="https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702201107-597a7b3d-sm.png"
- alt="Same diagram. Added on OpenWRT, AllowedIP setting for Smartphone." /></a>
+{% linked_image
+ url="https://pics.uvokchee.de/upload/2023/07/02/20230702201107-597a7b3d.png"
+ img="https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702201107-597a7b3d-sm.png"
+ alt="Same diagram. Added on OpenWRT, AllowedIP setting for Smartphone."
+%}
Well, oops. I still had the smartphone set up as a possible client on OpenWRT.
Apparently, the ping from my smartphone went through my VPS to OpenWRT just fine
@@ -76,9 +82,11 @@ on Wireguard for Android. Let everything Wireguard-internal
route via OpenWRT.
(Reminder: longest prefix wins. `/24` is longer than `/0`).
-<a href="https://pics.uvokchee.de/upload/2023/07/02/20230702203947-9169ae4a.png"><img
- src="https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702203947-9169ae4a-sm.png"
- alt="Same diagram, fixed AllowedIPs on smartphone." /></a>
+{% linked_image
+ url="https://pics.uvokchee.de/upload/2023/07/02/20230702203947-9169ae4a.png"
+ img="https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702203947-9169ae4a-sm.png"
+ alt="Same diagram, fixed AllowedIPs on smartphone."
+%}
Et voilá! ping still works.