From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id D1B8D1FF0A7 for ; Tue, 18 Aug 2026 10:52:35 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 3EBE421580; Tue, 18 Aug 2026 10:52:33 +0200 (CEST) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: [PATCH docs] network: Discourage the use of balance-{alb,tlb} Date: Tue, 18 Aug 2026 10:52:21 +0200 Message-ID: <20260818085228.125344-1-m.sandoval@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1787043127069 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.990 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 2C2HXCUZ5D2GOQUMFB4GAAPD5HY7QQI4 X-Message-ID-Hash: 2C2HXCUZ5D2GOQUMFB4GAAPD5HY7QQI4 X-MailFrom: m.sandoval@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: when used upstream of a bridge with VM traffic. Signed-off-by: Maximiliano Sandoval --- pve-network.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pve-network.adoc b/pve-network.adoc index 4209092..092096a 100644 --- a/pve-network.adoc +++ b/pve-network.adoc @@ -519,6 +519,10 @@ If your switch supports the LACP (IEEE 802.3ad) protocol, then we recommend using the corresponding bonding mode (802.3ad). Otherwise you should generally use the active-backup mode. +WARNING: The bond modes 'balance-alb' and 'balance-tlb' are not suitable when +the local addresses are not known to the host. These bond modes should not be +used behind a Linux bridge where virtual machines are connected to. + For the cluster network (Corosync) we recommend configuring it with multiple networks. Corosync does not need a bond for network redundancy as it can switch between networks by itself, if one becomes unusable. Some bond modes are known -- 2.47.3