Vlan over LAGG with LACP- release 18.1 on A10 quad core

[eldaservice]

Hi,
i created a LAGG with LACP over 2 nic, assigned it  and all works perfectly.
I tried to create a vlan over LAGG but the http interface hang and if reset it i can't see the vlan and the LAGG stop to work.
I tried to create the LAGG with only one NIC, i creted the vlan, ok i assigned them. Finally i added the second NIC to the LAGG. It seems to work perfectly but at the first reset the problems appears and the lagg not work properly.
The http interface itercept a problem and i sent it.
I think it's but. What i can do?
 

[DFC]

Sort of necroposting, but anyway - I have very similiar trouble.
I've got an OPNsense virtual appliance on VMWare. It had 3 virtual NICs (vmxnet3) and on LAN interface I've got some VLANs and everything worked good until...
So, I wanted to aggregate 2 NICs for LAN. For this I installed new physical NIC into the server (HP Proliant DL580 Gen8) - HP 361T (based on Intel i350 chip) with 2 1GBe ports. Then I turned on passthrough for it on VMWare host and added to OPNSense guest VM. After that, I configured LACP LAGG interface (with igb0 and igb1 members) and it was working well without 802.1q VLANs. Naturally, my next step was to add VLANs on that new interface, and here I got the kernel panic, when the parent interface is LAGG. And it happens every time I try. I submitted the issue report, but decided to post it here also.
Needless to say, that all hardware features are turned off (CRC, TSO, LRO, Vlan filtering).
Also, adding Vlans on igb0 or igb1 without aggregation works well.
May be there is something else, I could try to do?

[DFC]

Damn, it had gone away after I re-created the LAGG interface!
 

[mimugmail]

LAGG/LACP and VLANs is very error prone. If I remember correctly you have to create VLANs / LAGG in the right order (probably in combination with CARP).

[DFC]

Yesturday I caught couple of kernel panics while trying to do something with LAGG interface. lagg0 was assigned to LAN with IP address 192.168.0.2 (I was running another VM with OPNsense as default router for my net). And I created all Vlans I wanted. So, I shut down the reserve VM and tried to change IP address on LAN interface on master VM to 192.168.0.1 - got segfault. Then, after reboot, I tried to change assignment of LAN interface from lagg0 to vmx0 - and got second segfault. Submitted another bug report from GUI.

[guest7876]

ive been running Lagg on both our wan side and lan side of our OpnSense boxes. works well and i havent had any issues with it. No Carp involved. Running 18.1.8 though ive been running LAGG like this for many versions of OpnSense.

we are on Baremetal, No VM's or Hypervisors.

[DFC]

Today the master VM cannot boot properly. It segfaults in about 1 min after booting to shell. Could get it running only after detaching passthrough NICs.

[DFC]

ive been running Lagg on both our wan side and lan side of our OpnSense boxes...

Which NICs do you use?