Snapp

New Member
Mar 15, 2022
1
0
1
34
Hi, I have installed proxmox on an OVH cloud, following a restart of the cluster I can no longer reach the VMs of one of my subnets.
In practice I have a vm that has the wan in the subnet 192.168.3.x / 24 and from the cluster it is not reachable.

below I am attaching the configurations set on the cluster:

Bash:
cat /etc/network/interfaces

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual
        address <Public IP>
        gateway <Public gateway IP>

iface eno2 inet manual

iface enp0s20f0u8u3c2 inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports none
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet static
        address 192.168.2.1/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0

        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up   iptables -t nat -A POSTROUTING -s '192.168.2.0/24' -o eno1 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s '192.168.2.0/24' -o eno1 -j MASQUERADE

auto vmbr2
iface vmbr2 inet static
        address 192.168.3.1/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0

        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up   iptables -t nat -A POSTROUTING -s '192.168.3.0/24' -o eno1 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s '192.168.3.0/24' -o eno1 -j MASQUERADE


Bash:
ip -c link

...
40: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000

Bash:
 arp -a
? (x.x.x.x) at XX:XX:XX:XX:XX:XX [ether] on eno1
? (x.x.x.x) at XX:XX:XX:XX:XX:XX  [ether] on eno1
? (192.168.2.15) at 32:c3:6f:c4:1b:ed [ether] on vmbr1
? (192.168.2.105) at 72:9c:36:cf:2b:8c [ether] on vmbr1
? (x.x.x.x) at XX:XX:XX:XX:XX:XX  [ether] on eno1
? (192.168.2.95) at 3a:6a:e7:4f:3e:e0 [ether] on vmbr1
? (192.168.2.106) at 12:f2:74:8d:f4:47 [ether] on vmbr1
? (192.168.2.77) at 1e:d2:c1:f5:c9:eb [ether] on vmbr1

Bash:
ip r s

192.168.2.0/24 dev vmbr1 proto kernel scope link src 192.168.2.1    
192.168.3.0/24 dev vmbr2 proto kernel scope link src 192.168.3.1


ping 192.168.3.105
PING 192.168.3.105 (192.168.3.105) 56(84) bytes of data.
From 192.168.3.1 icmp_seq=1 Destination Host Unreachable
From 192.168.3.1 icmp_seq=2 Destination Host Unreachable
From 192.168.3.1 icmp_seq=3 Destination Host Unreachable
From 192.168.3.1 icmp_seq=4 Destination Host Unreachable
From 192.168.3.1 icmp_seq=5 Destination Host Unreachable
From 192.168.3.1 icmp_seq=6 Destination Host Unreachable

Could someone tell me what the problem is?
thank you in advance
 

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!