This looks promising! I'm in a similar boat - trying to remember what I did years ago and trying to sort out what in the world the naming convention is suppose to be.
Do the changes to /etc/modprobe.d/mlx4_core.conf go away then or can you...
Going back to simple bridge/enable vlan and specify tag on LXC...
my switch registers the mac and shows it in the assigned vlan but no dhcp and no traffi
if I tcp dump the nic port I see
09:20:47.221613 LLDP, length 271: ArubaS2500-24P-US...
having LXC vlan issues myself and found this. Does creating a linuxVlan on the interface then a bridge on that vlan not do the same thing / work for you?
vlan on interface, bridge on vlan, bridge NOT vlan aware, LXC vlan not set
auto enp5s0v2
iface enp5s0v2 inet manual
auto enp5s0v2.25
iface enp5s0v2.25 inet manual
auto vmbr1
iface vmbr1 inet manual
bridge-ports enp5s0v2.25...
just gonna start putting the iterations ive tried up here...
the standard vlan aware bridge, vlan tag in LXC
auto enp5s0v2
iface enp5s0v2 inet manual
auto enp5s0v3
iface enp5s0v3 inet manual
auto vmbr1
iface vmbr1 inet manual...
Beating my head against the wall for something that should just work.
Create new linuxBridge on second NIC (vmbr1) click vlan aware, add allowed vlan(s), give it an ip address. Can ping from from router.
assign this bridge to LXC, DHCP and vlan...
Kinda stumped:
Standard 192.x.x.x DHCP/firewall/switch network for fileserver/prox on 1Gb. Seperate 10Gbe network using dumb switch/static routes on 10.x.x.x for fileserver
BTW fileserver is baremetal OMV so no intra host netorking.
Working...