freebsd stable - Nov 2015 - LACP with 3 interfaces.

On Tue, Nov 17, 2015 at 8:26 AM, Johan Hendriks <joh.hendriks at
gmail.com> wrote:
> Is there something we can do to make sure lagg0 uses all the interfaces.
Nope.  LACP doesn't actively load balance its interfaces.  Each flow
gets assigned to a single interface based on a hash of the source and
destination MACs, IP addresses, and TCP/UDP ports.  With many clients,
all interfaces will probably be used, but with few clients, there's a
lot of luck involved.  If you want more bandwidth, you can try
fiddling with IP addresses and port numbers to influence the hash
function, but even if you get it to distribute the way you want, all
your work may be undone by a reboot.  The best option is to buy a
10Gbps NIC for the server.  They aren't too expensive, anymore, though
the switches are still pricey.  A cheaper option, if you'll only ever
have 4 clients, is to discard the lagg and assign a separate IP
address to each igb port, then manually distribute those addresses
amongst your clients.  If you do this, you unfortunately won't gain
the reliability features of LACP.

-Alan

Hi!
> > Is there something we can do to make sure lagg0 uses all the
interfaces.
> 
> Nope.  LACP doesn't actively load balance its interfaces.
On FreeBSD 11

	man lagg(4)

says:

The driver currently supports the aggregation protocols failover (the
default), lacp, loadbalance, roundrobin, broadcast, and none.

with

     roundrobin   Distributes outgoing traffic using a round-robin scheduler
                  through all active ports and accepts incoming traffic from
                  any active port.

If the three ports are needed for sending, shouldn't this work ?

-- 
pi at opsec.eu            +49 171 3101372                         5 years to go
!