On 2014/03/12 10:41, sven falempin wrote: > Hello, does someone knows about this and how to fix it or workaround ? > Best Regards, > > >Synopsis: LACP TRUNK IS NOT WORKING AS EXPECTED > >Category: system > >Environment: > System : OpenBSD 5.4 > Details : OpenBSD 5.4 (GENERIC) #37: Tue Jul 30 12:05:01 MDT 2013 > > [email protected]:/usr/src/sys/arch/i386/compile/GENERIC > > Architecture: OpenBSD.i386 > Machine : i386 > >Description: > Configuring trunk with LACP is broken. Cannot issue ICMP from > one trunk to another. This is done is a sandbox network. using to qemu > hosted openBSD. Strange FACT the id of the trunk stay 0000 Each > interface are direclty bridged to each other on the host, the bridge > is not shared, theres is one bridge per interface; > vio0(bsd1) <---> tapXXX <---> br0 <---> tapYYY <---> vio0(bsd2) > vio1(bsd1) <---> tapXXX <---> br0 <---> tapYYY <---> vio1(bsd2)
Your explanation is missing something, "tapXXX" and "br0" don't exist in OpenBSD and you haven't explained where they come from. Are you aware that LACP is a link-local protocol and is only expected to work over a single ethernet hop? From the naming "br0" I am suspecting some kind of bridge on some OS that you haven't talked about; if such a bridge *did* forward link-local frames (as would be needed for LACP to work), that would be a bug. You might do better with qemu socket network devices (or the L2TPv3 support that was recently added to qemu head), which should allow a "direct" connection between the virtual interfaces, rather than using a bridge device that exists outside the VMs.
