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

Get started on my own blog

Browse Source
This commit is contained in:
Lol3rrr
2026-02-17 00:09:09 +01:00
commit 12bf8b7ef8
12 changed files with 186 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
content/homelab-ipv4-expose/index.md Normal file
View File

@@ -0,0 +1,20 @@
+++
title = "Homelab - IPv4 Expose"
date = 2026-02-16
description = "How I expose my IPv6 only Homelab for IPv4 clients"
draft = true
[taxonomies]
categories = ["Homelab"]
tags = ["Homelab", "IPv4", "IPv6"]
+++
## Current Setup
Currently I am renting a VPS which runs a custom proxy, that loads the configuration from consul based on tags and then accepts traffic on the proper ports and forwards it manually.
## Plan
Services that need to be exposed get their own virtual IPv6 address using keepalived. The active/master node will be forced to the node on which the service is currently running using priorities.
On my external server setup Jool with SIIT-DC and iptable rules.
1. Everything coming in at the given port for the service (for example HTTP, Teamspeak, etc.) is redirected to a different internal IPv4 address using iptables
2. Jool listens on the internal IPv4 address and performs SIIT-DC or SIIT-EAM forwarding to the correct virtual IPv6 address