8021q not working

[garysday]

Hi Guys,

This seems really basic, I just did a fresh install for 9.1 (9.1.18), promox comes up, it looks for for now, then I try to do something simple - simply move the mgmt VLAN from vmbr0 to vmbr0.100 (I want it on a different subnet), I have enabled VLAN aware on the vmbr0 interface.

No matter how it try it (Gui or modifying /etc/network/interfaces), it doesn't take, I try to manually create a vlan with ip link add link command and I get unknown type.
Modprobe 8021q shows it's missing .. I don;'t want to do apt-get add for this as it tells me it will uninstall some other promos components.

just trying to do something simple

auto vmbr0.100
iface vmbr0.100 inet manual

ifreload -a shows
error: netlink: vmbr0.100: cannot create vlan vmbr0.100 100: operation failed with 'Operation not supported' (95)

Is this a 9.1 fresh install issue, or am I really missing something simple here

 

[aaron]

Can you please post the full /etc/network/interfaces within

blocks? (or use the code format buttons of the editor. If you use the SDN, please also add the /etc/network/interfaces.d/sdn file too.

 

[garysday]

Hi Aaron,

If could either be like this

auto lo
iface lo inet loopback

iface nic7 inet manual

iface nic0 inet manual

iface nic1 inet manual

iface nic2 inet manual

iface nic3 inet manual

iface nic4 inet manual

iface nic5 inet manual

iface nic6 inet manual

auto vmbr0
iface vmbr0 inet static
    address 10.1.1.243/24
    gateway 10.1.1.1
    bridge-ports nic7
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 100-120

auto vmbr0.100
iface vmbr0.100 inet static

or if I do what I'm trying and moving the vlan, then it would be like this

iface nic6 inet manual

auto vmbr0
iface vmbr0 inet static
        bridge-ports nic7
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 100-120

auto vmbr0.100
iface vmbr0.100 inet static
        address 192.168.100.10/24
        gateway 192.168.100.1

I can see that if is disable autostart then the configuration applies, but the vmbr interface is still showing as inactive..

Basically I'm trying to do something pretty simple which is just move the mgmt VLAN from untagged (VL1) on the main vmbr0 interface to a tagged segment.. that's all..

 

[garysday]

this is a vanilla install, when I try to force the if up , I get this output ..

root@proxmox1:~# ifup vmbr0.100 --force -v
info: requesting link dump
info: requesting address dump
info: requesting netconf dump
info: loading builtin modules from ['/usr/share/ifupdown2/addons']
info: module openvswitch not loaded (module init failed: no /usr/bin/ovs-vsctl found)
info: module openvswitch_port not loaded (module init failed: no /usr/bin/ovs-vsctl found)
info: module ppp not loaded (module init failed: no /usr/bin/pon found)
info: executing modprobe -q bonding
info: bond: error while loading bonding module: cmd 'modprobe -q bonding' failed: returned 1
info: module batman_adv not loaded (module init failed: no /usr/sbin/batctl found)
info: executing /sbin/sysctl net.bridge.bridge-allow-multiple-vlans
info: module mstpctl not loaded (module init failed: no /sbin/mstpctl found)
info: executing /bin/ip rule show
info: executing /bin/ip -6 rule show
info: address: using default mtu 1500
info: address: max_mtu undefined
info: executing /sbin/sysctl net.ipv6.conf.all.accept_ra
info: executing /sbin/sysctl net.ipv6.conf.all.autoconf
info: executing /usr/sbin/ip vrf id
info: mgmt vrf_context = False
info: executing /bin/ip addr help
info: address metric support: OK
info: module ppp not loaded (module init failed: no /usr/bin/pon found)
info: module mstpctl not loaded (module init failed: no /sbin/mstpctl found)
info: module batman_adv not loaded (module init failed: no /usr/sbin/batctl found)
info: module openvswitch_port not loaded (module init failed: no /usr/bin/ovs-vsctl found)
info: module openvswitch not loaded (module init failed: no /usr/bin/ovs-vsctl found)

 

[aaron]

Can you try and specify the bridge-vids 100-120 to start at 101 in the second example? Because the dedicated interface wants to assing itself a VLAN that the bridge already has.

By the way, you could also add it as it would look when you use the VLAN interface in the GUI:

iface nic6 inet manual

auto vmbr0
iface vmbr0 inet static
        bridge-ports nic7
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 100-120

auto mgmt
iface mgmt inet static
        address 192.168.100.10/24
        gateway 192.168.100.1
        vlan-raw-device vmbr0
        vlan-id 100

(should work, but I just changed it free-hand without verifying, so beware)

This way the mgmt interface has a better matching name