From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: superseded: [PATCH docs] network: Discourage the use of balance-{alb,tlb}
Date: Fri, 28 Aug 2026 11:58:13 +0200 [thread overview]
Message-ID: <s8o5x0ur2h6.fsf@toolbox> (raw)
In-Reply-To: <20260818085228.125344-1-m.sandoval@proxmox.com> (Maximiliano Sandoval's message of "Tue, 18 Aug 2026 10:52:21 +0200")
Maximiliano Sandoval <m.sandoval@proxmox.com> writes:
> when used upstream of a bridge with VM traffic.
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> 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
Superseded-by: https://lore.proxmox.com/all/20260828095721.263382-1-m.sandoval@proxmox.com/T/#u
--
Maximiliano
prev parent reply other threads:[~2026-08-28 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 8:52 [PATCH docs] network: Discourage the use of balance-{alb,tlb} Maximiliano Sandoval
2026-08-18 9:09 ` Gabriel Goller
2026-08-27 7:31 ` Aaron Lauterer
2026-08-28 9:58 ` Maximiliano Sandoval
2026-08-28 9:58 ` Maximiliano Sandoval [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s8o5x0ur2h6.fsf@toolbox \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox