From 0596c18939d1353fee2c2181c8846eae49793c97 Mon Sep 17 00:00:00 2001 From: Lol3rrr Date: Sun, 18 Oct 2026 22:17:07 +0200 Subject: [PATCH] Add the homelab-ipv4-epxpose series --- content/homelab-ipv4-expose-2/index.md | 2 ++ content/homelab-ipv4-expose/index.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/content/homelab-ipv4-expose-2/index.md b/content/homelab-ipv4-expose-2/index.md index 2cf1d3b..051f262 100644 --- a/content/homelab-ipv4-expose-2/index.md +++ b/content/homelab-ipv4-expose-2/index.md @@ -6,9 +6,11 @@ description = "Deploying my new IPv4 expose setup" [taxonomies] categories = ["Homelab"] tags = ["Homelab", "IPv4", "IPv6"] +series = ["homelab-ipv4-expose"] [extra] toc = true +series_order = 2 +++ Implementing the ideas and conclusions from my initial post about exposing my IPv6 Homelab to IPv4 clients ([Homelab IPv4 Expose](@/homelab-ipv4-expose/index.md)) in the real world and deploying the entire system. diff --git a/content/homelab-ipv4-expose/index.md b/content/homelab-ipv4-expose/index.md index cec4669..b9bd762 100644 --- a/content/homelab-ipv4-expose/index.md +++ b/content/homelab-ipv4-expose/index.md @@ -6,9 +6,11 @@ description = "How I expose my IPv6 only Homelab for IPv4 clients" [taxonomies] categories = ["Homelab"] tags = ["Homelab", "IPv4", "IPv6"] +series = ["homelab-ipv4-expose"] [extra] toc = true +series_order = 1 +++ How I plan to expose the services running in my homelab to IPv4 users despite not having a publicly routable IPv4 address/subnet.