You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be worth remembering that VLANs sit above bonding in the protocol stack, so the VLAN subinterfaces should not be created out of the member links.
I would suggest you limit the bonding (non-LAG) functionality to links without VLAN encapsulation (= access links but not trunks).
The bonding plugin needs more work in combination with VLANs, the following does not work correctly:
Need to create integration test cases for the basic use case with Linux hosts, and the VLAN case
The text was updated successfully, but these errors were encountered: