From cffed9b2a703bda44174f4b47020ed7fedfcc1f1 Mon Sep 17 00:00:00 2001
From: uvok cheetah
Date: Sun, 6 Oct 2024 12:27:27 +0200
Subject: Update image tag use
---
_posts/2023-07-02-shoot-foot-wireguard.md | 32 +++++++++++++--------
...22-was-verursacht-in-google-cloud-die-kosten.md | 10 +++++--
.../2024-09-04-convention-report-east-12-2024.md | 33 +++++++++++-----------
3 files changed, 44 insertions(+), 31 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?
-
+{% 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...
-
+{% 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.
-
+{% 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`).
-
+{% 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.
diff --git a/_posts/2024-02-22-was-verursacht-in-google-cloud-die-kosten.md b/_posts/2024-02-22-was-verursacht-in-google-cloud-die-kosten.md
index 329b4f6..0c8446d 100644
--- a/_posts/2024-02-22-was-verursacht-in-google-cloud-die-kosten.md
+++ b/_posts/2024-02-22-was-verursacht-in-google-cloud-die-kosten.md
@@ -22,7 +22,10 @@ verflucht. Ist das absichtlich so kompliziert gestaltet?
Jedenfalls, durch ein bisschen Recherche konnte ich einen wertvollen Tipp finden.
Man muss unter den Berichten nach "SKU" gruppieren. Und siehe da:
-
+{% image
+ img="https://pics.uvokchee.de/upload/2024/02/22/20240222203430-b677fc33.png"
+ alt="Screenshot vom Google Cloud Abrechnungsdashboard"
+%}
In meinem Fall war "Balanced PD Capacity" der Verursacher.
Etwas weitere Recherche zeigte, dass das der Speichertyp ist, der
@@ -30,7 +33,10 @@ von Google standardmäßig eingestellt wird, wenn man die 10 GB-Disk
anpasst (z.B. auf 30 GB) - "Gleichmäßig ausgelasteter nichtflüchtiger Speicher".
Die "richtige", gratis-Option ist allerdings "nichtflüchtiger Speicher".
-
+{% image
+ img="https://pics.uvokchee.de/upload/2024/02/22/20240222204655-5d171c61.png"
+ alt="Auswahlmöglchkeiten für Speicher in Gogle Cloud"
+%}
Ich mein, was ist das bitte für eine Übersetzung? Wir reden hier von Google. Die müssen
es sich doch leisten können, da was sinnvolles, verständliches hinzuschreiben? ;)
diff --git a/_posts/2024-09-04-convention-report-east-12-2024.md b/_posts/2024-09-04-convention-report-east-12-2024.md
index a1bc229..7c71898 100644
--- a/_posts/2024-09-04-convention-report-east-12-2024.md
+++ b/_posts/2024-09-04-convention-report-east-12-2024.md
@@ -87,13 +87,12 @@ Earlier, I was also in the games room, where a fellow furry brought a remodeled
slot machine. Yay. Very cool. Also, I met
[Karpour](https://conreports.karpour.net/) and Henrieke there.
-
-
-
+{% linked_image
+ url="https://pics.uvokchee.de/picture.php?/161/category/10"
+ img="https://pics.uvokchee.de/_data/i/upload/2024/09/04/20240904171913-a78a20ea-me.jpg"
+ alt="A slot machine (as used in gambling) redesigned with furry pictures,
+ named Furrymint"
+%}
Then there was of course the opening. I remembered wearing ear plugs this year,
and thus could enjoy the show very much, with a very nice light show.
@@ -148,11 +147,11 @@ forgot to take my meds. I didn't need much of a breakfast, still forced somethin
down. Sadly, I missed the Kaiserschmarrn that way. (But they had it again on
Monday!). Even if I didn't eat much, I had a nice talk with Elenir and Shippo.
-
+{% image
+ img="https://pics.uvokchee.de/_data/i/upload/2024/09/04/20240904171914-b3b2101a-me.jpg"
+ alt="A poster showing a boyband, the Barkstreet Boys featuring staff
+ members."
+%}
Back at the Ringberg, I played a round of "Exploding Kittens", I think we were
seven or eight furs playing together? That took quite some time, but was funny.
@@ -173,11 +172,11 @@ in love with a brown cheetah partial fursuit by Sasa creations, which led to an
episode of me "losing" my backpack somewhat later, luckily I just left it
somewhere where it still was when I looked.
-
+{% image
+ img="https://pics.uvokchee.de/_data/i/upload/2024/09/04/20240904171912-dbeea8e0-me.jpg"
+ alt="Yet another fictional boyband poster, this time announcing The power of
+ (paw icon)"
+%}
I think I didn't have lunch that day, and have a complete black hole in my memory
--
cgit v1.2.3