Having issues figuring out networking

Red Squirrel

Renowned Member
May 31, 2014
33
7
73
I'm trying to figure out networking but running into issues.

So the node has two NICs, ens32 is management, connected to my management vlan, as a regular connection. Ens34 is a trunk port to the switch. So I tried to follow various tutorials on how to setup the vlans, but no matter what I did, I could not get any vlans to show up as an option when assigning an interface to a vlan. I only see the physical nics as an option. If I pick the physical nic and then assign the vlan within the vm, the vm sees nothing. It doesn't get an IP or anything (I have dhcp running on the vlan I tested with)

Through deleting and trying stuff and overall trying to figure this out, I seem to have bricked the networking. I get this error now when I try to save, even a basic config.

In this particular config I'm just trying to restore it back to what it was before I played with it, and it won't let me go back anymore.


Code:
warning: vmbr1: <bridge.bridge object at 0x71f392121110>: error getting dependent interfaces (misconfiguration of bridge attribute(s) on existing non-bridge interface (vmbr1))
warning: vmbr1: <bridge.bridge object at 0x71f392121110>: error getting dependent interfaces (misconfiguration of bridge attribute(s) on existing non-bridge interface (vmbr1))
warning: vmbr1: invalid use of bridge attribute (bridge-ports) on non-bridge stanza
warning: vmbr1: invalid use of bridge attribute (bridge-stp) on non-bridge stanza
warning: vmbr1: invalid use of bridge attribute (bridge-fd) on non-bridge stanza
warning: vmbr1: invalid use of bridge attribute (bridge-vlan-aware) on non-bridge stanza
warning: vmbr1: invalid use of bridge attribute (bridge-vids) on non-bridge stanza



Screenshot from 2024-11-23 23-16-05.png
 
Last edited:
Running ifreload -a -d seems to have fixed it. Without -d I was getting these errors but -d somehow fixed it.

I just want to be clear though, by setting the vmbr1 (vlan aware) trunk interface on a vm, and specifying the vlan at the vm level, the VM is still only seeing that vlan correct? Ex: The VM OS is not seeing a trunk prt, but is equivalant to being plugged into an ethernet switch with a port set to that vlan? I just want to make sure I'm doing this right from a security perspective. I'm used to the vmware way where you need to create individual vlan interfaces too so want to make sure I'm not suppose to still do that for Proxmox as well.
 

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!