As already known, I use a Proxmox setup on servers of the German host Hetzner for myself and my customers. The wiki article about the Proxmox configuration is unfortunately not really up-to-date or easy to understand…
Often my readers asked me to pour the basic network configuration into an article: said, done – here’s the article!
In principle, you don’t have to prepare much to use a simple Proxmox setup.
Of course we need a dedicated server with installed Proxmox image and an additional IP from the Hetzner robot. We assume the following IP addresses:
- dedicated main IP
- IP: 220.127.116.11
- Gateway: 18.104.22.168
- Additional IPs (ordered via Robot – without MAC address!)
We also enable IP forwarding by executing the following command:
sysctl -w net.ipv4.ip_forward=1
We permanently enable forwarding by inserting the corresponding line in /etc/sysctl.d/99-hetzner.conf or removing the comment character.
More preparation is not necessary in this case.
Configuration Proxmox Host
On the Proxmox host, the /etc/network/interfaces file looks like this:
auto eth0 iface eth0 inet static address 22.214.171.124 netmask 255.255.255.255 gateway 126.96.36.199 pointopoint 188.8.131.52 auto vmbr0 iface vmbr0 inet static address 184.108.40.206 netmask 255.255.255.255 bridge_ports none bridge_stp off bridge_fd 0 bridge_maxwait 0 up ip route add 220.127.116.11/32 dev vmbr0 up ip route add 18.104.22.168/32 dev vmbr0 up ip route add 22.214.171.124/32 dev vmbr0 up ip route add 126.96.36.199/32 dev vmbr0
It is important here to enter the main IP (here: 188.8.131.52) for the eth0 and vmbr0 devices as a quasi „double“ entry. The gateway address must also be entered at gateway and pointopoint – Attention: pointopoint has only one t in the middle, this is not a typo!
A reboot later should display two network devices – eth0 and vmbr0.
Virtual Machine Configuration (Linux)
After the installation I change the file /etc/network/interfaces as follows:
auto eth0 iface eth0 inet static address 184.108.40.206 netmask 255.255.255.255 pointopoint 220.127.116.11 gateway 18.104.22.168
After a restart the VM should be reachable via ping as well as via SSH.
Virtual Machine Configuration (Windows)
Sometimes you also need a Windows machine, which is why I would like to show the configuration here simply by screenshot:
The option „Check settings on exit“ must not be activated, since Windows – just like Debian – checks the configuration and would report an error – despite these error messages of the The virtual machines are running completely stable.
The configuration is actually quite simple and very clear. By adding a single line in the network configuration, additional IP addresses can be added and superfluous ones removed. The configuration runs very stable, you don’t have to bother with DHCP servers and the performance is also satisfactory.
I hope I have been able to help some readers – and of course Google visitors – with my instructions and of course I am happy to support you in setting up your own setup – just contact me for a non-binding offer!
Questions, criticism and hints to the article I accept naturally gladly in the comments – please have however also understanding that I can offer free support only in certain framework.