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

[Johannes Ernst]

Sure? Do you have additional information? I think it’s not correct and it works!

Debian 7: kernel: 3.11

No problem with tagging on a bridge. Proxmox using the same way to create it.

root at test:~# uname -a
Linux test 3.11-0.bpo.2-amd64 #1 SMP Debian 3.11.10-1~bpo70+1 (2013-12-17) x86_64 GNU/Linux
root at test:~# 

bridge name	bridge id		STP enabled	interfaces
vmbr1		8000.866041adf40c	no		eth1

root at test:~# vconfig add vmbr1 10
Added VLAN with VID == 10 to IF -:vmbr1:-

root at test:~# ip link set vmbr1.10 up

root at test:~# ifconfig

vmbr1.10  Link encap:Ethernet  HWaddr 86:60:41:ad:f4:0c  
          inet6 addr: fe80::8460:41ff:fead:f40c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:328 (328.0 B)

root at test:~# brctl addbr vmbr2

root at test:~# brctl addif vmbr2 vmbr1.10
root at test:~# brctl show
bridge name	bridge id		STP enabled	interfaces
vmbr1		8000.866041adf40c	no		eth1
vmbr2		8000.866041adf40c	no		vmbr1.10


I using this with >3.10 and different hosts to do tagging over tinc. It only abstract the interface with an additional bridge. Bridge ports can be also used as tagged device.

Mixed tagging is not be possible with this patch, you can only choose for bridge tagging or normal interface tagging over the trigger.

It’s time for VXLAN?


Am 10.01.2014 um 14:23 schrieb Stefan Priebe - Profihost AG <s.priebe at profihost.ag>:

> Yes and it also does not work with vlan starting with kernel 3.9 or 3.10.
> 
> Stefan
> 
> Am 10.01.2014 14:20, schrieb 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 
>> _______________________________________________
>> pve-devel mailing list
>> pve-devel at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20140110/f3109161/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20140110/f3109161/attachment.sig>