[pve-devel] [PATCH pve-docs 1/2] add vlanaware bridge management vlan configuration

Alexandre DERUMIER aderumier at odiso.com
Tue Sep 11 07:31:48 CEST 2018


>>This example is exactly the same as the previous one. The only difference is that you use bond0 instead of eno1? If so, I don't think it is worth to add.

yes, I was not sure if we need to show it.
I'll remove it and send a v2.




----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>, "aderumier" <aderumier at odiso.com>
Envoyé: Mardi 11 Septembre 2018 06:25:23
Objet: Re: [pve-devel] [PATCH pve-docs 1/2] add vlanaware bridge management vlan configuration

comments/questions inline 

> On September 10, 2018 at 5:31 PM Alexandre Derumier <aderumier at odiso.com> wrote: 
> 
> 
> --- 
> pve-network.adoc | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++-- 
> 1 file changed, 53 insertions(+), 2 deletions(-) 
> 
> diff --git a/pve-network.adoc b/pve-network.adoc 
> index 1ac5b28..d61619f 100644 
> --- a/pve-network.adoc 
> +++ b/pve-network.adoc 
> @@ -407,7 +407,7 @@ function of VLAN 5 in the guest network, but in combination with VLAN anwareness 
> bridge this it will not work for guest network VLAN 5. 
> The downside of this setup is more CPU usage. 
> 
> -.Example: Use VLAN 5 for the {pve} management IP 
> +.Example: Use VLAN 5 for the {pve} management IP with traditional Linux bridge 
> ---- 
> auto lo 
> iface lo inet loopback 
> @@ -432,11 +432,32 @@ iface vmbr0 inet manual 
> bridge_fd 0 
> 
> ---- 
> +.Example: Use VLAN 5 for the {pve} management IP with VLAN aware Linux bridge 
> +---- 
> +auto lo 
> +iface lo inet loopback 
> + 
> +iface eno1 inet manual 
> + 
> + 
> +auto vmbr0.5 
> +iface vmbr0.5 inet static 
> + address 10.10.10.2 
> + netmask 255.255.255.0 
> + gateway 10.10.10.1 
> + 
> +auto vmbr0 
> +iface vmbr0 inet manual 
> + bridge_ports eno1 
> + bridge_stp off 
> + bridge_fd 0 
> + bridge_vlan_aware yes 
> +---- 

looks good 

> 
> The next example is the same setup but a bond is used to 
> make this network fail-safe. 
> 
> -.Example: Use VLAN 5 with bond0 for the {pve} management IP 
> +.Example: Use VLAN 5 with bond0 for the {pve} management IP with traditional Linux bridge 
> ---- 
> auto lo 
> iface lo inet loopback 
> @@ -471,6 +492,36 @@ iface vmbr0 inet manual 
> 
> ---- 
> 
> +.Example: Use VLAN 5 with bond0 for the {pve} management IP with VLAN aware Linux bridge 
> +---- 
> +auto lo 
> +iface lo inet loopback 
> + 
> +iface eno1 inet manual 
> + 
> +iface eno2 inet manual 
> + 
> +auto bond0 
> +iface bond0 inet manual 
> + slaves eno1 eno2 
> + bond_miimon 100 
> + bond_mode 802.3ad 
> + bond_xmit_hash_policy layer2+3 
> + 
> +auto vmbr0.5 
> +iface vmbr0.5 inet static 
> + address 10.10.10.2 
> + netmask 255.255.255.0 
> + gateway 10.10.10.1 
> + 
> +auto vmbr0 
> +iface vmbr0 inet manual 
> + bridge_ports bond0 
> + bridge_stp off 
> + bridge_fd 0 
> + bridge_vlan_aware yes 
> +---- 

This example is exactly the same as the previous one. The only difference is that you use bond0 instead of eno1? If so, I don't think it is worth to add. 

> + 
> //// 
> TODO: explain IPv6 support? 
> TODO: explain OVS 
> -- 
> 2.11.0 
> 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel at pve.proxmox.com 
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 



More information about the pve-devel mailing list