to have my LAN clients: computers, IoT devices and so on reach the LXC servers inside the ProxMox Cloud Cluster SDN they all need a routing into 10.10.20.0/24. Alas the VF NetBox does not provide any means to create static routes. So I decided to advertise my routing via DHCP
I switched OFF the...
i created Debian test machines on the other nodes called sdntest01 and sndtest02. I chose 10.10.20.0/24 as the subnet for all LXC joining the SDN
as you can see sdntest01 is able to see sdntest02 across the compute nodes.
to enable the SDN to send traffic into the WireGuard tunnel I had the...
The second part of this experiment focusses on linking the LAN to the ProXMox Cloud Cluster. I decided to go with WireGuard and got myself a gl.Inet Mango Router from Amazon (~20 €).
steps I went:
as I utilize the Vodafone ConnectBox (or NetBox) I got for free from VF I had no chance to...
i have created a hyperconverged ProxMox Cloud Cluster as an experimental project.
using 1blu.de compute nodes: 1 Euro / month
using 1blu.de storage node 1 TB: 9 Euro / month
using LAN based on Vodafone Cable Internet IPV6 DS-LITE (VF NetBox)
the ProxMox cluster uses...
You can use standard iptables features on the ProxMox host:
iptables -t nat -A PREROUTING -d YOUR-PUBLIC-STATIC-IP/32 -p tcp -m tcp --dport YOUR-EXTERNAL-PORT -j DNAT --to-destination YOUR-CONTAINER-IP:YOUR-CONTAINER-PORT
For my VPS Proxmox 6.2 hosted in the cloud i did the following, that is similar to your tutorial but shorter.
enable paket forwarding in /etc/sysctl.conf on the Proxmox host
edit /etc/network/interfaces on the ProxMox host, to get 10.10.10.0/24 for your containers, that route through eth0...