On Fri, Mar 27, 2020 at 12:11 PM Per Jessen <per@computer.org> wrote:
Roger Oberholtzer wrote:
In openSUSE, would this be related to bonding slaves?
LACP is quite old, I wonder if Netgear is providing the hardware version, i.e. let the switch do the work? We have had network interface bonding in Linux for at least 10-12 years, also with LACP. We are using it, but I don't recall needing anything special in the switches. (I didn't do the setup).
The switch I referenced said it supported IEEE 802.3ad - LAGs (LACP). I am curious how the switch could manage this. That is, how would the server know to send out data on the various interfaces when they are aggregated later? I would imagine that the switch would assign an address to the aggregated ports. It's how the server knows this and acts accordingly that I'm curious about. At the end of the day, I would just want to ensure that openSUSE LEAP would be able to use this feature without anything strange required. https://en.wikipedia.org/wiki/Link_aggregation#Linux_bonding_driver seems to imply that the linux bonding driver is a software version of this. The switch would, it seems, do something else. So it is an either/or thing. Perhaps it is best if the switch be let do it. Or? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org