[PVE-User] Proxmox 5 (LACP/Bridge/VLAN120)

[Alexandre DERUMIER]

Just a note, 

if you create a bond0.120,

then after you create also vm on this vlan, proxmox will enslave a bridge on this bond0.120, and you can't
have ip on interface, when this interface is enslave in bridge. (so you'll lost connection).

another way to prevent this, is to create a bridge

vmbr0v120    (like proxmox do),  enslave bond0.120 in this bridge, and setup ip addres on the vmbr0v120 brige.


(personnaly, I'm using vlan aware, it's working fine)


----- Mail original -----
De: "Uwe Sauter" <uwe.sauter.de at gmail.com>
À: "proxmoxve" <pve-user at pve.proxmox.com>
Envoyé: Mercredi 23 Août 2017 07:30:25
Objet: Re: [PVE-User] Proxmox 5 (LACP/Bridge/VLAN120)

Sorry, I mixed up the IP addresses. MTU according to what you switch supports (in this case jumbo frames with 9000 bytes). 

/etc/network/interfaces 
----------------------------------------- 
# management interface 
auto eth0 
iface eth0 inet static 
address 192.168.0.2 
netmask 255.255.255.0 
gateway 192.168.0.254 

# 1st interface in bond 
auto eth1 
iface eth1 inet manual 
mtu 9000 

# 2nd interface in bond 
auto eth2 
iface eth2 inet manual 
mtu 9000 

# bond 
auto bond0 
iface bond0 inet manual 
slaves eth1 eth2 
bond-mode 802.3ad 
bond-miimon 100 
mtu 9000 

# interface for vlan 120 on bond with IP 
auto bond0.120 
iface bond0.120 inet static 
address 10.100.100.8 
netmask 255.255.255.0 
mtu 9000 

# interface for vlan 130 on bond without IP (just for VMs) 
auto bond0.130 
iface bond0.130 inet manual 

----------------------------------------- 


Am 23.08.2017 um 07:27 schrieb Uwe Sauter: 
> An example out of my head: 
> 
> 
> /etc/network/interfaces 
> ----------------------------------------- 
> # management interface 
> auto eth0 
> iface eth0 inet static 
> address 10.100.100.8 
> netmask 255.255.255.0 
> gateway 10.100.100.254 
> 
> # 1st interface in bond 
> auto eth1 
> iface eth1 inet manual 
> mtu 9000 
> 
> # 2nd interface in bond 
> auto eth2 
> iface eth2 inet manual 
> mtu 9000 
> 
> # bond 
> auto bond0 
> iface bond0 inet manual 
> slaves eth1 eth2 
> bond-mode 802.3ad 
> bond-miimon 100 
> mtu 9000 
> 
> # interface for vlan 120 on bond with IP 
> auto bond0.120 
> iface bond0.120 inet static 
> address 192.168.123.2 
> netmask 255.255.255.0 
> mtu 9000 
> 
> # interface for vlan 130 on bond without IP (just for VMs) 
> auto bond0.130 
> iface bond0.130 inet manual 
> 
> ----------------------------------------- 
> 
> 
> Am 23.08.2017 um 06:44 schrieb Alexandre DERUMIER: 
>> Hi, 
>> 
>> you can create a bond0.120 interface and setup ip on it. 
>> 
>> (and keep bond0 in bridge). 
>> 
>> 
>> another way, enable "vlan aware" option in bridge. (see gui), 
>> 
>> then you can create a 
>> 
>> vmbr0.120, and setup ip on it. 
>> 
>> 
>> ----- Mail original ----- 
>> De: "Devin Acosta" <devin at pabstatencio.com> 
>> À: "proxmoxve" <pve-user at pve.proxmox.com> 
>> Envoyé: Mercredi 23 Août 2017 03:40:07 
>> Objet: [PVE-User] Proxmox 5 (LACP/Bridge/VLAN120) 
>> 
>> I need to configure Proxmox 5.x with the following. 
>> 
>> Bond of 2 interfaces using LACP 
>> Bridge off Bond0, with IP on VLAN 120 (10.100.100.8/24) 
>> The network switch doesn’t have native VLAN, so the IP has to be on the 
>> TAGGED VLAN 120. 
>> 
>> Please help. ;) 
>> 
>> Devin 
>> _______________________________________________ 
>> pve-user mailing list 
>> pve-user at pve.proxmox.com 
>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 
>> 
>> _______________________________________________ 
>> pve-user mailing list 
>> pve-user at pve.proxmox.com 
>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 
>> 
> 

_______________________________________________ 
pve-user mailing list 
pve-user at pve.proxmox.com 
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user