Proxmox Bridged on Hetzner routing - guest can access network, but can't connect to other VMs

asandor

New Member
Sep 30, 2020
2
0
1
34
There's a two node PVE solution, where the second, newer install has some routing issues: the VMs on the node can access public internet, can download packages, I can SSH to them from local machine, etc., but when trying to connect to them from the VMs of the other node, they're unavailable: ping shows Destination Host Unreachable SSH from VMs on different subnet shows No route to host. I checked routing setup of the new PVE node and it shows an incorrect address, that I'm not sure where it's coming from:

Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 enp35s0 10.0.0.248 0.0.0.0 10.0.0.3 U 0 0 0 vmbr0

/etc/network/interfaces

auto lo iface lo inet loopback iface lo inet6 loopback auto enp35s0 iface enp35s0 inet static address server address gateway 10.0.0.1 iface enp35s0 inet6 static address xxxxxxx/64 gateway xxxx auto vmbr0 iface vmbr0 inet static address 10.0.0.249 netmask 10.0.0.3 bridge-ports none bridge-stp off bridge-fd 0

I flushed the route, but had no effect. I tried to remove the route with "ip route del 10.0.0.248 via 0.0.0.0" and the response was "RTNETLINK answers: No such process"


10.0.0.1 proxmox gateway
10.0.0.2 proxmox public server gateway
10.0.0.249 correct gateway
10.0.0.248 is an incorrect address
10.0.0.3 netmask

Any suggestions?
 

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!