[pve-devel] [PATCH docs] remove wrongly configured vmbr from bond example
Thomas Lamprecht
t.lamprecht at proxmox.com
Thu Jan 9 11:07:43 CET 2020
On 1/9/20 9:36 AM, Dominik Csapak wrote:
> the vmbr0 used eno1 as bridge_port, but it is already
> in use by bond0, making the example wrong (as in, it does not work) and
> confusing
I mean the routes get setup correctly and all interfaces get created with
the respective config, so it's a bit debatable.. But, it would be always a
strange setup to have, so no objection to address this.
>
> since the example is about ip addresses on bonds, remove the vmbr0
>
> Signed-off-by: Dominik Csapak <d.csapak at proxmox.com>
> ---
> pve-network.adoc | 9 ---------
> 1 file changed, 9 deletions(-)
>
> diff --git a/pve-network.adoc b/pve-network.adoc
> index c61cd42..31cc168 100644
> --- a/pve-network.adoc
> +++ b/pve-network.adoc
> @@ -343,15 +343,6 @@ iface bond0 inet static
> bond_mode 802.3ad
> bond_xmit_hash_policy layer2+3
>
> -auto vmbr0
> -iface vmbr0 inet static
> - address 10.10.10.2
> - netmask 255.255.255.0
> - gateway 10.10.10.1
> - bridge_ports eno1
> - bridge_stp off
> - bridge_fd 0
> -
> ----
>
>
>
makes not much sense for a proxmox setup where guests are expected, I'd remove this
whole example and just keep the one below which correctly has the bond0 as slave
for vmbr0.. Or add a third network interface which is then used for the bridge.
A hint that using a single port directly for as slave-port for more than one other
interface does not work could be also good.
More information about the pve-devel
mailing list