[pve-devel] [PATCH] Virtual vlan tagging to bridge interface

[Alexandre DERUMIER]

Hi,
If I remember Stefan Priebe use this kind of configuration and had send patchs last year.

But it was breaking some setup for me, with kernel 2.6.32.

I think this kind of config was broken (mixing tagging on eth and bridge)

eth0 -> eth0.tag -> bridge0 -> vm 
eth0 -> bridge1 -> bridge1.tag -> bridge2 -> vm 


----- Mail original ----- 

De: "Johannes Ernst" <info at filemedia.de> 
À: pve-devel at pve.proxmox.com 
Envoyé: Vendredi 10 Janvier 2014 14:17:33 
Objet: Re: [pve-devel] [PATCH] Virtual vlan tagging to bridge interface 

Hello, 


normally proxmox adds the vlan tag to the physical device (eth) like eth0.1 and creates then a bridge interface. If you using tunnel (gre, ipsec,..) or other interfaces vconfig cannot add a tagged interface. 


I changed the function to add interfaces to every device with an additional bridge. It creates a bridge (bridge1) to the interface and the tagged interface for it (bridge1.x). Then it creates another bridge and add this tagged bridge port to the new bridge (bridge2). Proxmox adds to this bridge the tap device of the vm. 



You can trigger the solution over the datacenter.cfg. If you want to enable the virtual bridge solution add 'virtual_tagging: 1’ to the datacenter.cfg. Normally it use the default version. 


For example: 


1) normal solution 


eth0 -> eth0.tag -> bridge1 -> vm 


2) virtual tagged solution 


eth0 -> bridge1 -> bridge1.tag -> bridge2 -> vm 



Live print: 



vmbr1 8000.666d7626577a no dummy0 
eth2 




vmbr1v1 8000.666d7626577a no tap113i1 
vmbr1.1 


It should be nice if everyone can test it too. 






A short description for that patch would be helpful. 



_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel