[SOLVED] Other WAN / Public IPs not reachable from VMs in NAT Network

TaktischerSpeck

New Member
Jun 12, 2022
2
0
1
Hello,
I use Proxmox on a Hetzner Dedicated Server with the Following Setup:

Dedicated-Proxmox, vmbr0: Public IP X.X.X.117, vmbr1: Internal NAT IP 192.168.0.1/24
VM-Plesk (Public IP: X.X.X.110)
VM-Panel (Internal NAT IP 192.168.0.120)
VM-Host-1 (Public IP: X.X.X.113)

Plesk is Running Debian, Panel Ubuntu 22.04.1.

From the Panel I can Ping:
1.1.1.1
8.8.8.8
Gateway for Subnet
X.X.X.117(Proxmox)

Every other IP of the Subnet except for I cant ping:

X.X.X.110
X.X.X.113
Also a ping to a DNS record or a wget does not work.
.110 and .113can Ping / SSH to 192.168.0.120

Any idea how i can fix that / what i am doing wrong?
 
Last edited:
Do you know the moment you look away from a problem for some time and then look back, and you have a new idea?

I added a route on the Proxmox machine, and now it works.
I think the issue is that the Public IP VMs are connected to vmbr0 and the internal network is on another vNIC vmbr1.

So I just executed this:
ip route add X.X.X.110/32 dev vmbr0
ip route add X.X.X.113/32 dev vmbr0

This only is active until the next restart, so I added this in /etc/network/interfaces
Code:
post-up ip route add X.X.X.110/32 dev vmbr0
post-up ip route add X.X.X.113/32 dev vmbr0
 

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!