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

Write more content for the ipv4-expose-2

Browse Source
This commit is contained in:
Lol3rrr
2026-05-20 11:58:22 +02:00
parent 1005d0a57c
commit c1cb840ce2
1 changed files with 28 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -127,6 +127,9 @@ runcmd:
```
{% end %}
The configuration essentially does everything mentioned in the first post of this mini-series + setting up wireguard.
## 2. Extend ipv-proxy
In its original state, the ipv-proxy could only do "manual" forwarding and connect to a single consul address, which both needs to be reworked.
@@ -141,22 +144,30 @@ Previously one could only pass a single address and if that had issues, then the
However now, I can pass the addresses of all my consul servers and it will try all of them until one responds, which means I no longer have a single point of failure in this regard.
## 3. Wireguard setup
This is required for my use-case, because ipv-proxy needs access to my consul cluster regardless of any proxy status or issues and to ensure this, I simply setup a wireguard network.
Specifically in my case, all of my internal servers act as wireguard servers listening on their public IPv6 address for connections and then the external server connects to all of them for redundancy.
# Deployment
## Hosting Provider
Hard Requirements:
* Provides at least 1 public routable IPv4 address
* Provides at least a /33 IPv6 subnet
* /32 for the NAT64
* 1 address for the server itself
* Supports automation using terraform and cloud-init
* Reliable
Soft Requirements:
* Competitive prices
* European provider
My choice: [Scaleway](https://www.scaleway.com/)
TODO: Explain
## Automation
The entire deployment is completly automated using terraform and cloud-init, as mentioned earlier.
TODO
# Final Overview
<!-- 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 -->
# Final Thoughts
TODO