Proxmox networking confusion (bond, vmbr, cluster)

[Matt998]

Hello there,
been trying to set up a cluster with three nodes + SAN on Proxmox 8.X. Currently setting the first node (no cluster at the moment)

Network specs:

• two 10G ports for iSCSI, each on a different vlan, connected to a different switch, with multipath, no bonding: this works OK
• two 1G ports for management, connected to a different switch, switch indipendent bonding (balance-alb): this works OK
• two 10G ports for corosync: each on a different vlan, connected to a different switch, no bonding. Still have to configure corosync
• two 10G ports for VM traffic: this is the part that I struggle with.

At the switch side, the ports for VM Traffic are configured as a trunk: I'd like to map a specific VLAN to specific guest, and I don't know how to do it.

At the proxmox side, those two ports are currently configured as a switch-indipendent bond (bond0) using balance-alb.
Then I created a vmbr0 interface on top of the bond0 interface (and set it VLAN aware).
Then, I added an interface to the guest: I can only select "vmbr0" and I tried to specify the VLAN there. It doesn't work.

Then, I tried to go to Datacenter -> pve1 -> System -> Network -> Create Linux VLAN with the following settings:

• Name: vmbr0.18
• vlan raw device: vmbr0
• vlan tag: 18

Then, I tried to assign that interface to the guest... but I cannot do it! It only allows me to select vmbr0 as the interface.

What am I doing wrong?

Thanks

here is my /etc/network/interfaces file:

# 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 eno8303
iface eno8303 inet manual

auto ens2f2
iface ens2f2 inet static
    address 10.54.54.10/24
#corosync-2

iface ens2f3 inet manual

auto eno8403
iface eno8403 inet manual

auto ens1f0
iface ens1f0 inet static
    address 10.33.33.113/24
#iscsi-1

auto ens1f1
iface ens1f1 inet manual
    bond-master bond0
    offload-rxvlan off
    offload-txvlan off
    offload-tso off
    offload-rx-vlan-filter off

auto ens1f2
iface ens1f2 inet static
    address 10.53.53.10/24
#corosync-1

iface ens1f3 inet manual

auto ens2f0
iface ens2f0 inet static
    address 10.34.34.113/24
#iscsi-2

auto ens2f1
iface ens2f1 inet manual
    bond-master bond0
    offload-rxvlan off
    offload-txvlan off
    offload-tso off
    offload-rx-vlan-filter off

auto bond0
iface bond0 inet manual
    bond-slaves ens1f1 ens2f1
    bond-miimon 50
    bond-mode balance-alb
    offload-rxvlan off
    offload-txvlan off
    offload-tso off
    offload-rx-vlan-filter off
#VM Traffic

auto bond1
iface bond1 inet static
    address 192.168.182.110/24
    gateway 192.168.182.1
    bond-slaves eno8303 eno8403
    bond-miimon 100
    bond-mode balance-alb
#Management

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

auto vmbr0.18
iface vmbr0.18 inet manual
#servizi

source /etc/network/interfaces.d/*

 

[cheiss]

Hi,

I'd like to map a specific VLAN to specific guest, and I don't know how to do it.

so you would like all traffic of an guest to go through a VLAN?
That can be done using the tag option of the individual network interface.

This can either be done by editing the network interface in the web interface and setting VLAN tag or using qm set, but there you have to specify the full network interface config.

 

[Matt998]

thanks! I tried with another VLAN, and it did work by specifying the VLAN on the network interface of the guest.

Turns out that the problem was a "conflict" with the IP ranges: the VLAN 18 that I tried to use with the guest has the ip network of 192.168.182.0/24, which is the same of the management address of the Proxmox server. What could I do, to make both addressing works?

Thanks