+++
title = "Homelab - IPv4 Expose - Deployment"
date = 2026-05-20
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
[Jool](https://github.com/NICMx/Jool) is a tool that implements a bunch of IPv6 and IPv4 translation mechanisms.
This does the heavy lifting, when it comes to actually processing the packets and performing the low-level translations.

## Stateful NAT64
[Stateful NAT64](https://nicmx.github.io/Jool/en/run-nat64.html) is one of the mechanisms to translate between IPv6 and IPv4 networks.
It works similarly to normal NAT, with the addition of not only mapping ports and addresses, but mapping between an IPv6 and IPv4 address.
So one side of the translation has a unique IPv6 address + port combination and the other side is a unique IPv4 address + port combination.

## ipv-proxy
[ipv-proxy](https://github.com/Lol3rrr/ipv-proxy) is a custom tool, I developed, which dynamically reads configuration from consul to expose IPv6 services to IPv4 clients.
This usually runs on some external server, which can do both IPv4 and IPv6.
Services in consul can then add specific tags, which are found by the ipv-proxy, which then exposes the IPv6 only service from the IPv4 address of the server, by forwarding all the traffic.

Previously this only worked with TCP and was doing the forwarding naively in user-space software, but as part of this I added support for using jool to do the actual forwarding.

# Plan
Okay so there are a couple of goals/requirements I have for this deployment:
1. The entire setup should be automated and portable between vendors
2. Extend ipv-proxy to natively use jool for forwarding
3. Use wireguard for connecting to my internal consul cluster

## 1. Automated and portable setup
To make sure my setup is repeatable and portable between different providers, I decided to fully rely on cloud-init.
{% details(summary="cloud-init config") %}
```
#cloud-config
ssh_authorized_keys:
  - ${macbook_ssh_key}
  - ${ubuntu_ssh_key}

package_update: true
package_upgrade: true

packages:
  - jool-dkms
  - jool-tools
  - ndppd

write_files:
  - path: /etc/sysctl.d/99-forwarding.conf
    permissions: '0644'
    content: |
      net.ipv4.conf.all.forwarding=1
      net.ipv6.conf.all.forwarding=1
      net.ipv6.conf.all.proxy_ndp=1
  - path: /etc/ndppd.conf
    permissions: '0666'
    content: |
      proxy ens2 {
          rule ${ipv6_prefix} {
              static
          }
      }
  - path: /etc/modules-load.d/jool
    permissions: '0666'
    content: |
      jool
  - path: /usr/local/bin/ipv-proxy
    permissions: '0777'
    source:
      uri: https://github.com/Lol3rrr/ipv-proxy/releases/download/${ipv_proxy_version}/ipv-proxy
  - path: /etc/systemd/system/ipv-proxy.service
    content: |
      [Unit]
      Description=Proxy IPv4 traffic to IPv6
      After=cloud-init.target
      Wants=cloud-init.target

      [Service]
      Type=simple
      ExecStart=/usr/local/bin/ipv-proxy %{ for addr in consul_addrs ~}--consul-addr ${addr} %{ endfor ~} --backend jool --public-ip ${proxy_ipv4_public} --jool-pool6-subnet ${proxy_ipv6_subnet}

      [Install]
      WantedBy=multi-user.target

wireguard:
  interfaces:
    - name: wg0
      config_path: /etc/wireguard/wg0.conf
      content: |
        [Interface]
        Address = 10.200.0.200/32
        MTU = 1280
        PrivateKey = ${wg_private_key}

%{ for peer in wg_peers ~}
        [Peer]
        # Name ${peer.name}
        PublicKey = ${peer.public_key}
        AllowedIPs = ${peer.ip}/32
        Endpoint = ${peer.endpoint}
        PersistentKeepalive = 25
%{ endfor ~}

runcmd:
  - "sysctl -w net.ipv4.conf.all.forwarding=1"
  - "sysctl -w net.ipv6.conf.all.forwarding=1"
  - "sysctl -w net.ipv6.conf.all.proxy_ndp=1"
  - "sysctl --system"
  - "modprobe jool"
  - "systemctl daemon-reload"
  - "systemctl enable ipv-proxy.service"
  - "systemctl start --no-block ipv-proxy.service"
```
{% end %}

## 2. Extend ipv-proxy
In its original state, the ipv-proxy could only do "manual" forwarding.
Therefore I first extended it, to support different backends for performing the actual forwarding.
It also now supports multiple addresses for consul, which it will try round-robin style, until one works.

## 3. Wireguard setup
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 -->