[PATCH docs] network: Discourage the use of balance-{alb,tlb}

[PATCH docs] network: Discourage the use of balance-{alb,tlb}

[Maximiliano Sandoval]

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
-- 
2.47.3

Re: [PATCH docs] network: Discourage the use of balance-{alb,tlb}

[Gabriel Goller]

LGTM, Consider:
Reviewed-by: Gabriel Goller <g.goller@proxmox.com>

Re: [PATCH docs] network: Discourage the use of balance-{alb,tlb}

[Aaron Lauterer]

On  2026-08-18  10:52, Maximiliano Sandoval wrote:
> 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.

not sure how I should interpret the "behind" here. Maybe we can phrase 
that differently?

nic1 & nic2 --> bond0 --> bridge0 --> guests

I assume it is this setup?
Though reading the text, my brain is inclined to think the bond is 
between the bridge and guests...

Maybe a rephrasing to:

These bond modes should not be used when a Linux bridge with guests is 
used in combination with the bond.



> +
>   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