802.3ad LACP consistently employs identical interface during data transfer from the server.
802.3ad LACP consistently employs identical interface during data transfer from the server.
I'm working on configuring LACP between your Debian machine and the TP-Link T1600G-18TS switch. I've enabled mode-4 bonding on two interfaces on the server and set up LACP on the switch. When transferring files via SMB or Rsync, only one interface is used consistently, even though the other remains idle. Removing the active interface causes traffic to switch to the unused port, and reinserting it restores normal routing. Splitting traffic across both interfaces works when using SRC MAC or SRC + DST MAC hashing on the switch. I've tested various hashing methods on the switch but none affected the outcome. The server side hasn't changed its behavior yet, and I'm still unsure how altering the hashing settings might help.