Probably a BUG in managing Vlans on renamed interfaces.

[yena]

Probably a BUG in managing Vlans on renamed interfaces.
I tried to rename the interfaces to get around the Bug of interfaces with too long names indicated in my previous post, but they are not seen and the Vm is not started.


root@MSWstg4:~# cat /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="90:e2:ba:75:77:c0", NAME="w"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="90:e2:ba:75:77:c1", NAME="L"


root@MSWstg4:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eno2 inet manual

iface eno1 inet manual

iface enp131s0f0 inet manual

iface eno3 inet manual

iface eno4 inet manual

iface enp131s0f1 inet manual

iface w inet manual

iface L inet manual

iface w.210 inet manual <--- Test to declare the vlan .. same result .. with or without
vlan-raw-device w

auto vmbr0
iface vmbr0 inet static
address 188.240.228.84/26
gateway 188.240.228.65
bridge-ports w.210
bridge-stp off
bridge-fd 0
#WAN

auto vmbr1
iface vmbr1 inet static
address 192.168.13.84/24
bridge-ports L.110
bridge-stp off
bridge-fd 0
#LAN

source /etc/network/interfaces.d/*
root@MSWstg4:~#
root@MSWstg4:~# brctl show vmbr0
bridge name bridge id STP enabled interfaces
vmbr0 8000.90e2ba7577c0 no w.210
root@MSWstg4:~#
root@MSWstg4:~# qm start 797979
no physical interface on bridge 'vmbr0'
kvm: -netdev type=tap,id=net0,ifname=tap797979i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on: network script /var/lib/qemu-server/pve-bridge failed with status 6400
start failed: QEMU exited with code 1

 

[yena]

pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-8-pve)
pve-manager: 8.3.4 (running version: 8.3.4/65224a0f9cd294a3)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8: 6.8.12-8
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.2.0
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.2
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.3-1
proxmox-backup-file-restore: 3.3.3-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.6
pve-cluster: 8.0.10
pve-container: 5.2.4
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-3
pve-ha-manager: 4.0.6
pve-i18n: 3.4.0
pve-qemu-kvm: 9.0.2-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1

 

[UdoB]

Probably a BUG in managing Vlans on renamed interfaces.

There's an alternative approach to circumvent those long names:

J

Post in thread 'Setup one bridge per VLAN with OpenVswitch'

Mar 11, 2025

One solution is to rename the NIC from "enp1s0f0np0" to a shorter name like "lan0":

A better solution is to name the vlan something else:

auto vlan2540
iface vlan2540 inet manual
    vlan-raw-device enp1s0f0np0
#virt-eth vlan 2540


auto vmbr2540
iface vmbr10 inet manual
        bridge-ports vlan2540
        bridge-stp off
        bridge-fd 0
#bridge vlan 2540

This is fully supported in the UI (not sure what version introduced it) with a highlighted comment to encourage its use:


Just give it an arbitrary name, and set the raw device to the ethernet device.

• jhfry

•