ifupdown2 bridge-vids issues

[ctr]

I use a vlan-aware bridge on a Proxmox VE 6.1 system with a following network configuration:

auto vmbr0
iface vmbr0 inet manual
    bridge-ports eno7
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 2-4094
    bridge-pvid 1
    mtu 9000

However, my NIC (Intel X722, handled by i40e module) has a limit of number of VLANs for HW filtering so it switches to SW filtering with that number.

So I would like to reduce the number of bridge-vids from everything (2-4094) to the VLANs I actually need on the bridge. For multiple VLANs the syntax seems to be space separated (as per https://docs.cumulusnetworks.com/cu...hernet-Bridging-VLANs/VLAN-aware-Bridge-Mode/ ). If I just use a single VLAN ID i.e.

bridge-vids 10

everything is fine, also if use a single range, i.e.

bridge-vids 10-20

So I have to assume all is fine and it is not a NIC/driver issue (i.e. like https://forum.proxmox.com/threads/need-some-serous-help-quickly-please.61489/#post-282546 )

But when I use a space separated list, the VLANs are not accessible in the bridge anymore with no error message on network (re)start.

Since the ifupdown2 package is a -pve package (not Debian) I guess this is the right place to report the bug.

 

[spirit]

I use a vlan-aware bridge on a Proxmox VE 6.1 system with a following network configuration:

auto vmbr0
iface vmbr0 inet manual
    bridge-ports eno7
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 2-4094
    bridge-pvid 1
    mtu 9000

However, my NIC (Intel X722, handled by i40e module) has a limit of number of VLANs for HW filtering so it switches to SW filtering with that number.

So I would like to reduce the number of bridge-vids from everything (2-4094) to the VLANs I actually need on the bridge. For multiple VLANs the syntax seems to be space separated (as per https://docs.cumulusnetworks.com/cu...hernet-Bridging-VLANs/VLAN-aware-Bridge-Mode/ ). If I just use a single VLAN ID i.e.

bridge-vids 10

everything is fine, also if use a single range, i.e.

bridge-vids 10-20

So I have to assume all is fine and it is not a NIC/driver issue (i.e. like https://forum.proxmox.com/threads/need-some-serous-help-quickly-please.61489/#post-282546 )

But when I use a space separated list, the VLANs are not accessible in the bridge anymore with no error message on network (re)start.

Since the ifupdown2 package is a -pve package (not Debian) I guess this is the right place to report the bug.

Hi,

Maybe can you try to make a bug report to ifupdown2 github directly
https://github.com/CumulusNetworks/ifupdown2/issues

if you try also to reload network in debug mode, maybe it'll give you more infos:

#ifreload -a -d

 

[spirit]

Also what is the output of "bridge -c vlan show" ?

 

[ctr]

Thanks for the feedback!
However, it looks like ifupdown2 was replaced by ifupdown accidentally at some point which seems to have caused the issue.
So above stated issue exist on ifupdown, *not* ifupdown2. (Which is strange, I thought vlan-aware-bridges and bridge-vids were introduced with ifupdown2 only).

So for now everything is fine on my end. If you want me to troubleshoot this on ifupdown again let me know and I can post output.

 

[spirit]

well, proxmox have added bridge-vids && vlan-aware syntax in ifupdown1 scripts some years ago. (with inspirations from ifupdown2/cumulus syntax as vlan aware linux bridge code has been done by cumulus at this time).

But I'm not sure it's 100% compliant with ifupdown2 syntax.

the script was:
/etc/network/if-up.d/bridgevlan

        if [ -n "$IF_BRIDGE_VIDS" ]
        then
            bridge vlan add dev $port vid $IF_BRIDGE_VIDS
        else
            bridge vlan add dev $port vid 2-4094
        fi

So I think it's only works with a simple range only

 

[Szymons]

I can admit after few years ... that in proxmox 8 and latest ifupdown2 I have feelings that this bridge-vids is not working !
but I will create new topic and noone will say to me that I was not searching