[SOLVED] DHCP on vlan bridge only works after staring container

[Aluveitie]

I want the Proxmox management to be available in vlan 102.
The vmbr0 bridge is used by multiple VMs/CTs with different VLANS, which works so far.
What does not work is the vmbr0.102 getting an IP on boot, strangely it works after I start a container, then DHCP works and vmbr0.102 gets its IP assigned. If I define a static IP, it also only works after I start a container.

Except from the interfaces config.

auto enp129s0f0np0
iface enp129s0f0np0 inet manual

auto vmbr0.102
iface vmbr0.102 inet dhcp

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

I would have preferred to create an interface per VLAN, but then the name is 1 character over the limit...

 

[Aluveitie]

I could resolve the issue by renaming enp129s0f0np0 to eno3 and then set up a dedicated vlan interface instead:

iface eno3 inet manual

iface eno3.101 inet manual

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

auto vmbr0v101
iface vmbr0v101 inet dhcp
        bridge-ports eno3.101
        bridge-stp off
        bridge-fd 0

iface vmbr0v101 inet6 auto
        accept_ra 2
        up dhclient -1 -6 -cf /etc/dhcp/dhclient6.conf -lf /var/lib/dhcp/dhclient6.vmbr0v101.leases -v vmbr0v101 || true