On Fri, 2024-02-23 at 20:10 +0000, Andy Smith wrote:
> One more time: a successor to the Ethernet bonding driver already
> exists and has for more than 10 years.
That is the other thing I wanted to ask here, I have configured a
LACP link aggregating interface more or less similar to what is
described in the wiki, in my /etc/interfaces there is now:
auto bond0
iface bond0 inet static
address 10.0.16.2/24
bond-slaves en0 en1
bond-mode 4
bond-miimon 100
bond-downdelay 200
bond-updelay 200
bond-lacp-rate 1
bond-xmit-hash-policy layer3+4
which seems to work (I could not test throughput yet, because
I am waiting for cables).
If I do this, does "ifupdown" use "ifenslave" or does it
use "ip link set" as described here:
https://www.uni-koeln.de/~pbogusze/posts/LACP_configuration_using_iproute2.html
behind the scenes? Is the wiki/documentation lagging the actual
implementation? Is there a way to find out (other than removing
ifenslave and seeing if it still works)?
Should documentation in the wiki be updated?
Also, above still(?) contains "bond-slaves en0 en1" so if this is
a new implementation, is there still some terminology change to be
expected? Or can I replace bond-slaves with something else in the
current Debian bookworm?
/ralph
