Hetzner Cluster Networking

Iain Stott

New Member
Feb 11, 2017
4
2
1
40
So I've been playing with Proxmox on a few Hetzner servers as I want to learn the clustering and HA element of Proxmox. I have 3 hosts, all on different subnets and I have created 3 vSwitches and connected all hosts to the vSwitches. All servers have single NIC with single Public IP, but my first host has an additional /29.

My idea is that the cluster communication is setup on one VLAN, file sync between hosts on another, and then to setup private network between hosts for the VM's on the 3rd. I will then setup an Opnsense VM with the /29 attached and the private network VLAN to give internet access to the rest of the VM's and handle incoming traffic to the /29 and passthrough to the backends.

At the moment I have everything working apart from the private network VLAN, where I have network connectivity, I can ping out including to domain names, but when it comes to run yum update or wget or curl it times out.

I'm not a massive networking guy so I'm a bit stumped at the minute so any help would be appreciated.

Code:
auto enp3s0.4001
iface enp3s0.4001 inet manual
  vlan-raw-device enp3s0
  mtu 1400

auto vmbr0
iface vmbr0 inet manual
  bridge_ports enp3s0.4001
  bridge_stp off
  bridge_fd 0
  mtu 1400

I have also assigned an IP to VLAN interface

Code:
auto enp3s0.4001
iface enp3s0.4001 inet manual
  address 192.168.100.1
  netmask 255.255.255.0
  vlan-raw-device enp3s0
  mtu 1400

auto vmbr0
iface vmbr0 inet manual
  bridge_ports enp3s0.4001
  bridge_stp off
  bridge_fd 0
  mtu 1400
Thanks
Iain
 
At the moment I have everything working apart from the private network VLAN, where I have network connectivity, I can ping out including to domain names, but when it comes to run yum update or wget or curl it times out.


Code:
auto enp3s0.4001
iface enp3s0.4001 inet manual
  address 192.168.100.1
  netmask 255.255.255.0
  vlan-raw-device enp3s0
  mtu 1400

auto vmbr0
iface vmbr0 inet manual
  bridge_ports enp3s0.4001
  bridge_stp off
  bridge_fd 0
  mtu 1400


IP address has to be assigned to the bridge (vmbr0) not to its port (enp3s0.4001)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!