diff options
author | uvok cheetah | 2024-08-02 18:47:46 +0200 |
---|---|---|
committer | uvok cheetah | 2024-08-02 18:47:46 +0200 |
commit | e42caf33889c44b1aa8617a6670d1767765474fd (patch) | |
tree | 6cd4d9619d3a64b3c6673d309b8c2b196174000b | |
parent | 001baa553ffc7a494e7bdcf6132f1d38de2f4809 (diff) |
wireguard: Use HTML markup
less hassle
-rw-r--r-- | _posts/2023-07-02-shoot-foot-wireguard.md | 16 |
1 files changed, 12 insertions, 4 deletions
diff --git a/_posts/2023-07-02-shoot-foot-wireguard.md b/_posts/2023-07-02-shoot-foot-wireguard.md index 0a8f64b..8968624 100644 --- a/_posts/2023-07-02-shoot-foot-wireguard.md +++ b/_posts/2023-07-02-shoot-foot-wireguard.md @@ -16,7 +16,9 @@ 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 diagram showing the network components of my Wireguard setup.](https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702201107-0ecdfc52-sm.png)](https://pics.uvokchee.de/upload/2023/07/02/20230702201107-0ecdfc52.png) +<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> 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` @@ -32,7 +34,9 @@ to try to figure out what went wrong. Well, lets see, what are the AllowedIPs... -[![Same diagram as before. Added: AllowedIPs.](https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702201107-5df12e17-sm.png)](https://pics.uvokchee.de/upload/2023/07/02/20230702201107-5df12e17.png) +<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> Hm. Seems good enough. The smartphone pings to the VPS get answered all right. The AllowedIPs match there. @@ -51,7 +55,9 @@ ping from Smartphone to OpenWRT... Still stuck. The heck? Okay, let's see the configs again. Very carefully. -[![Same diagram. Added on OpenWRT, AllowedIP setting for Smartphone.](https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702201107-597a7b3d-sm.png)](https://pics.uvokchee.de/upload/2023/07/02/20230702201107-597a7b3d.png) +<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> 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 @@ -69,7 +75,9 @@ on Wireguard for Android. Let everything Wireguard-internal route via OpenWRT. (Reminder: longest prefix wins. `/24` is longer than `/0`). -[![Same diagram, fixed AllowedIPs on smartphone.](https://pics.uvokchee.de/i.php?/upload/2023/07/02/20230702203947-9169ae4a-sm.png)](https://pics.uvokchee.de/upload/2023/07/02/20230702203947-9169ae4a.png) +<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> Et voilá! ping still works. |