Selon Reyk Floeter <[EMAIL PROTECTED]>: > you should use failover mode with the non-manageable switch.
Allright. > this doesn't requires any configuration on the switch and even works > with hubs(!) because we drop packets received on non-active ports. there > was a bug in the 3.9 manpage: failover mode does NOT receive on all > member interfaces at the same time. Nice. OK, I understand better now. > -> is a simple alg and may increase the perfomance if both l2 endpoints > support roundrobin mode. > > roundrobin mode requires special configuration on the switch, using > protos like HP trunk or Cizzco ether/port-channel. you can also use > with a bunch of x-link cables between two systems using trunk or > connections over different switches/hubs. nevertheless, some switches > seem to have problems with openbsd running in roundrobin mode (some > Cizzco-Eeehs), so i implemented a third and hopefully the last mode: > loadbalance. OK, so indeed it's definitely not going to work here. > - balance outgoing traffic across the active ports based on > hashed protocol header information. the hash includes the > ethernet source and destination address, and, if available, the > vlan tag, and the ipv4/ipv6 source and destination address. > - receive on all active interfaces > - if one interface is unplugged, skip it and use the next active one. > - trunk keeps running, as long as at least one interface is active ;) Even if using a non-manageable switch or is it the same as roundrobin? > most of the vendors lie about the performance. you'll never get n times > of the performance in port trunks, ie. an 5000Mbps link by aggregating > 5 GigE interfaces... that's nonsense! since their default mode is Of course... I knew that ;) Thanks a lot for this big answer. I now understand much better how trunk works, I really appreciated! All the best. -- Antoine
