netdev - [Bonding Draft Proposal] Add lacp_prio Support for ad

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <aFpLXdT4_zbqvUTd@fedora>
Date: Tue, 24 Jun 2025 06:53:17 +0000
From: Hangbin Liu <liuhangbin@...il.com>
To: Jay Vosburgh <jv@...sburgh.net>
Cc: Andrew Lunn <andrew+netdev@...n.ch>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Subject: [Bonding Draft Proposal] Add lacp_prio Support for ad_select?

Hi Jay,

We have a customer setup involving two separate switches with identical
L2/VLAN configurations. Each switch forms an independent aggregator
(port-channel), and the end host connects to both with the same number of
links and equivalent bandwidth.

As a result, the host ends up with two aggregators under a single bond
interface. Since the user cannot arbitrarily override port count or
bandwidth, they are asking for a new mechanism, lacp_prio, to influence
aggregator selection via ad_select.

Do you think this is a reasonable addition?

If yes, what would be the best way to compare priorities?

1. Port Priority Only. Currently initialized to 0xff. We could add a parameter
   allowing users to configure it.
   a) Use the highest port priority within each aggregator for comparison
   b) Sum all port priorities in each aggregator and compare the totals

2. Full LACP Info Comparison. Compare fields such as system_priority, system,
   port_priority, port_id, etc.

At present, the libteam code has implemented an approach that selects the
aggregator based on the highest system_priority/system from both local and
partner data.[1]

Looking forward to your thoughts.

Best regards,
Hangbin

[1] https://github.com/jpirko/libteam/blob/master/teamd/teamd_runner_lacp.c#L402