cant access other subnets from pve node

slohr

New Member
Mar 21, 2022
3
0
1
41
hi,

I cant access any other subnets from my pve node.

i have a couple of vlans. at the moment my pve-node (pve) is in the management subnet (10.1.20.0/24 - vlan: 120) and the vms are all running in the service subnet (10.1.10.0/24 - vlan: 110).

i can access the proxmox ui from any subnet (of which the route is allowed to the subnet of course). the issue that i now have is that my nas is in the service subnet and i cant reach it from the pve host itself. i can only reach network target within the same subnet.

my current network configuration:

Code:
# 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

iface enp4s0 inet manual

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 10.1.20.10/24
        gateway 10.1.20.1
        bridge-ports enp4s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

auto vmbr1
iface vmbr1 inet static
        address 10.1.10.10/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

the host has two NICs and it even does not work if i would connect the second nic and force it (via switch) to the service-subnet. it also does not make any difference if i remove the vmbr1. also if the second one would be the gateway does not matter as well.

i wanted to seperate the proxmox host in a different subnet and not have it in the "normal" service network. however if i cant access the my nas for backup purposes and images it kinda defeats the purpose. :-/

i recently upgraded to pve8 but the issue was already there with v7.

any ideas or suggestions would be welcome.
 
What you did there is giving your PVE host an IP in two subnets but not inside a VLAN. If you want the PVE host to have an IP in the VLANs 110 and 120 you would need to use something like this:

Code:
# 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

iface enp4s0 inet manual

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet manual
        bridge-ports enp4s0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

iface vmbr0.120 inet static
        address 10.1.20.10/24
        gateway 10.1.20.1

iface vmbr0.110 inet static
        address 10.1.10.10/24
 

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!