leon/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Finish post

Browse Source
This commit is contained in:
Lol3rrr
2026-05-20 19:57:21 +02:00
parent c1cb840ce2
commit 3bef43d281
1 changed files with 8 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
content/homelab-ipv4-expose-2/index.md
View File

@@ -1,8 +1,7 @@
+++
title = "Homelab - IPv4 Expose - Deployment"
date = 2026-05-20
description = "Integrating the ideas from the previous post"
draft = true
description = "Deploying my new IPv4 expose setup"
[taxonomies]
categories = ["Homelab"]
@@ -12,13 +11,12 @@ tags = ["Homelab", "IPv4", "IPv6"]
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.
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.
<!-- 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.
This will cover some of the background needed for this setup, if you have already read the previous post or are familiar with jool, NAT64 and ipv-proxy, you can skip this section.
## Jool
[Jool](https://github.com/NICMx/Jool) is a tool that implements a bunch of IPv6 and IPv4 translation mechanisms.
@@ -162,12 +160,13 @@ Soft Requirements:
* Competitive prices
* European provider
My choice: [Scaleway](https://www.scaleway.com/)
TODO: Explain
I ultimately decided to go with [Scaleway](https://www.scaleway.com/), because they tick all the boxes for me.
## Automation
The entire deployment is completly automated using terraform and cloud-init, as mentioned earlier.
TODO
Using this combination allows me to completly automatically and easily spin up a new instance, and I am making use of that by never touching the existing instance for changes, but instead just recreating/replacing the entire thing.
# Final Thoughts
TODO
With everything combined, I now have a completly automated system for setting up my external proxy server and the proxying my services.
All I need to do in my day-to-day to expose something to IPv4 clients, is to add a corresponding tag to the service definition.