Re: Inclusive terminology (instead of master/slave) for network bonding/LACP

From	Ralph Aichinger <ra@h5.or.at>
Newsgroups	linux.debian.user
Subject	Re: Inclusive terminology (instead of master/slave) for network bonding/LACP
Date	2024-02-23 21:50 +0100
Message-ID	<IaKEx-c9rw-1@gated-at.bofh.it> (permalink)
References	<IaeEF-bPT3-1@gated-at.bofh.it> <IaF2a-c5SB-11@gated-at.bofh.it> <IaFbP-c5W8-7@gated-at.bofh.it> <IaHnk-c7s9-3@gated-at.bofh.it> <IaKbv-c9eM-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Thread

Inclusive terminology (instead of master/slave) for network  bonding/LACP Ralph Aichinger <ra@h5.or.at> - 2024-02-22 11:40 +0100
  Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 07:10 +0100
  Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 10:50 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-23 11:00 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 11:10 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP tomas@tuxteam.de - 2024-02-23 11:20 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 12:20 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Alain D D Williams <addw@phcomp.co.uk> - 2024-02-23 11:10 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 11:30 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-23 19:30 +0100
      Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Mike Castle <dalgoda+debian@gmail.com> - 2024-03-14 19:30 +0100
        Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-15 01:50 +0100
          Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Alain D D Williams <addw@phcomp.co.uk> - 2024-03-15 09:50 +0100
            Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Mike Castle <dalgoda+debian@gmail.com> - 2024-03-15 17:10 +0100
              Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-03-15 17:20 +0100
              Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-15 17:40 +0100
            Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-15 17:30 +0100
          Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Will Mengarini <seldon@eskimo.com> - 2024-03-15 19:20 +0100
            Please terminate this faecal matter - the whole thread appears to be  a troll.....Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Bret Busby <bret@busby.net> - 2024-03-15 20:00 +0100
              Re: Please terminate this faecal matter - the whole thread appears to  be a troll.....Re: Inclusive terminology (instead of master/slave) for  network bonding/LACP Jeffrey Walton <noloader@gmail.com> - 2024-03-15 23:30 +0100
            Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-15 21:50 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Arno Lehmann <al@its-lehmann.de> - 2024-02-23 12:50 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 13:20 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 13:40 +0100
      Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-24 23:30 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Karen Lewellen <klewellen@shellworld.net> - 2024-02-25 00:20 +0100
          Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-25 07:30 +0100
            Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-25 08:40 +0100
            Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-25 12:50 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 15:50 +0100
  Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 11:10 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Roger Price <roger@rogerprice.org> - 2024-02-23 11:50 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 12:20 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 15:40 +0100
    Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Jeffrey Walton <noloader@gmail.com> - 2024-02-23 17:30 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Dan Ritter <dsr@randomstring.org> - 2024-02-23 19:10 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Gremlin <scott-andrews@columbus.rr.com> - 2024-02-23 19:20 +0100
          Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Jeffrey Walton <noloader@gmail.com> - 2024-02-23 21:00 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-23 20:00 +0100
          Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-02-24 12:30 +0100
            Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP jeremy ardley <jeremy.ardley@gmail.com> - 2024-02-24 12:40 +0100
              Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-02-24 14:50 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP The Wanderer <wanderer@fastmail.fm> - 2024-02-24 15:10 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Alain D D Williams <addw@phcomp.co.uk> - 2024-02-24 18:00 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-24 19:40 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-24 23:20 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP <tomas@tuxteam.de> - 2024-02-25 07:20 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-25 08:40 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP tomas@tuxteam.de - 2024-02-25 10:30 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Geert Stappers <stappers@stappers.nl> - 2024-02-25 10:40 +0100
                Reply to list vs. group reply [was: Inlclusive terminology...] <tomas@tuxteam.de> - 2024-02-25 10:50 +0100
                Re: Reply to list vs. group reply [was: Inlclusive terminology...] Geert Stappers <stappers@stappers.nl> - 2024-02-25 13:20 +0100
                Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Andy Smith <andy@strugglers.net> - 2024-02-24 22:40 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Jeffrey Walton <noloader@gmail.com> - 2024-02-25 01:50 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-25 12:10 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Alain D D Williams <addw@phcomp.co.uk> - 2024-02-25 12:30 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-25 13:00 +0100
                Re: Postel's Law (Was Re: Inclusive terminology (instead of  master/slave) for network bonding/LACP) Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-02-25 02:00 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Emanuel Berg <incal@dataswamp.org> - 2024-03-14 18:00 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-24 21:50 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Marco Moock <mm@dorfdsl.de> - 2024-02-25 00:30 +0100
                Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-25 00:50 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-25 12:40 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Ralph Aichinger <ra@h5.or.at> - 2024-02-23 21:20 +0100
  Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 15:50 +0100
    Re: Inclusive terminology (instead of master/slave) for network bonding/LACP fxkl47BF@protonmail.com - 2024-02-23 16:00 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 18:20 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 21:20 +0100
          Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Ralph Aichinger <ra@h5.or.at> - 2024-02-23 21:50 +0100
            Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-23 22:20 +0100
          Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-24 03:40 +0100
            Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-24 04:00 +0100
              Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Zenaan Harkness <zenaan@gmail.com> - 2024-02-24 23:20 +0100
                Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Andy Smith <andy@strugglers.net> - 2024-02-24 23:30 +0100
    Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Mariusz Gronczewski <xani@devrandom.pl> - 2024-02-23 18:20 +0100
      Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Ralph Aichinger <ra@h5.or.at> - 2024-02-23 21:30 +0100
        Re: Inclusive terminology (instead of master/slave) for network  bonding/LACP Charles Curley <charlescurley@charlescurley.com> - 2024-02-23 22:40 +0100
  Re: Inclusive terminology (instead of master/slave) for network bonding/LACP Jeffrey Walton <noloader@gmail.com> - 2024-02-23 20:40 +0100

csiph-web