On Sat, Mar 15, 2014 at 11:07 AM, Stuart Henderson <s...@spacehopper.org> wrote: > On 2014-03-15, sven falempin <sven.falem...@gmail.com> wrote: >> Ok what i get is the bridge itself who announce the working link ? >> But if the switch is sending LACP what is this outgoing LACP packet >> (the one not forwaded by tun nor by a bridge) ? > > I forgot that the lacp needed to be sent by the switch/bridge. > > But if you had a tun/bridge in between the nic and the switch that should > also not be forwarding the LACP frames.
i removed the bridge, i just have tun0 (link0) and use ssh to forward ethernet on the other side. the lacp is entering the tun (i see it in tcpdump) but never came out the other side of the tunnel. is tun forwarding all type of ethernet broadcast ? > >> So lets say two machines got a bunch of nics and want to have a direct >> connection between them (no switch ) >> To get Failover(cable is long and may be unplugged) + Load balancing >> (need the bandwith) >> over the links, trunk0(LACP) is not an option . What else ? > > "trunkproto roundrobin" or "trunkproto loadbalance". > > I don't see what any of these buy you in your virtualized environment though, > surely you would need to deal with this in the VM host ? > >> I guess VLT Force10 answered that a few years ago. >> > > That's a proprietary protocol for running link aggregation from e.g. > a server to multiple switches. > -- --------------------------------------------------------------------------------------------------------------------- () ascii ribbon campaign - against html e-mail /\
