Get started with follow-up post for homelab ipv4 expose

content/_index.md

@@ -1,5 +1,5 @@
 +++
 title = "List of blog posts"
 sort_by = "date"
-paginate_by = 10
+paginate_by = 20
 +++

content/auto-server-setup/index.md

@@ -1,6 +1,6 @@
 +++
 title = "Automatic Server Setup"
-date = 2026-03-31
+date = 2026-06-01
 description = "Automatic my server setup"
 draft = true
 

content/homelab-ipv4-expose-2/index.md

@@ -0,0 +1,61 @@
++++
+title = "Homelab - IPv4 Expose - Deployment"
+date = 2026-04-25
+description = "Integrating the ideas from the previous post"
+draft = true
+
+[taxonomies]
+categories = ["Homelab"]
+tags = ["Homelab", "IPv4", "IPv6"]
+
+[extra]
+toc = true
++++
+
+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 
+using it.
+
+<!-- more -->
+
+# Background
+This will cover some of the background needed for this setup, if you have already read the previous post or are familiar with jool and NAT64, you can skip this section.
+
+## Jool
+Testing
+
+## NAT64
+Testing
+
+# Plan
+<!-- Automated Setup -->
+The entire setup should be automated and portable between vendors.
+
+<!-- ipv-proxy -->
+I want to continue using the ipv-proxy for handling all the dynamic forwarding stuff.
+
+<!-- wireguard for ipv-proxy -->
+To support ipv-proxy, it needs to connect to my internal consul cluster, to enable this access I use wireguard.
+
+# Extending ipv-proxy
+<!-- Now supports jool as a forwarding backend -->
+In its original state, ipv-proxy could only do the manual forwarding.
+Therefore I first had to extend it, to support different backends to perform the forwarding.
+
+<!-- Multiple consul-addr -->
+
+# New Setup
+<!-- Running on Scaleway -->
+This new setup is now using Scaleway as the hosting provider, there are a couple of reasons for this:
+* Provides a public routable IPv4 address
+* Provides a public routable IPv6 /64 subnet
+* Supports terraform for configuration/setup
+* Relatively competitive prices
+* European alternative
+
+but I am not using any vendor specific features and any relatively modern cloud provider should be suitable for this.
+
+<!-- Setup using Terraform + cloud-init -->
+Having choosen the cloud provider, its time to move to the setup/configuration of the system.
+For this purpose I decided to use terraform together with cloud-init to provision and configure the system.
+
+<!-- Wireguard -->

content/quickfacts-1/index.md

@@ -1,6 +1,6 @@
 +++
 title = "Quickfacts - Part 1: The Mental Model"
-date = 2026-04-02
+date = 2026-06-01
 description = "Building a Mental Model"
 draft = true
 

content/quickfacts-automata/index.md

@@ -1,6 +1,6 @@
 +++
 title = "Quickfacts - Automata Model"
-date = 2026-04-02
+date = 2026-06-01
 description = "Building an automata based model for factorio"
 draft = true
 

content/quickfacts-intro/index.md

@@ -1,6 +1,6 @@
 +++
 title = "Quickfacts - Intro"
-date = 2026-04-01
+date = 2026-06-01
 description = "An introduction to my Quickfacts project"
 draft = true
 

content/streaming/index.md

@@ -1,6 +1,6 @@
 +++
 title = "Streaming setup"
-date = 2026-03-31
+date = 2026-06-01
 description = "Custom streaming setup to complement teamspeak"
 draft = true
 

content/udmpro/index.md

@@ -1,6 +1,6 @@
 +++
 title = "Homelab - UDMPro"
-date = 2026-03-31
+date = 2026-06-01
 description = "Documenting my configuration for the UDMPro"
 draft = true