<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div apple-content-edited="true"><div><div style=" orphans: 2; widows: 2;">Sure? Do you have additional information? I think it’s not correct and it works!</div><div style=" orphans: 2; widows: 2;"><br></div><div style=" orphans: 2; widows: 2;"><div>Debian 7: kernel: 3.11</div><div><br></div><div>No problem with tagging on a bridge. Proxmox using the same way to create it.</div><div><br></div><div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">root@test:~# uname -a</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">Linux test 3.11-0.bpo.2-amd64 #1 SMP Debian 3.11.10-1~bpo70+1 (2013-12-17) x86_64 GNU/Linux</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">root@test:~# </div></div><div><br></div><div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">bridge name<span class="Apple-tab-span" style="white-space:pre"> </span>bridge id<span class="Apple-tab-span" style="white-space:pre"> </span>STP enabled<span class="Apple-tab-span" style="white-space:pre"> </span>interfaces</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">vmbr1<span class="Apple-tab-span" style="white-space:pre"> </span>8000.866041adf40c<span class="Apple-tab-span" style="white-space:pre"> </span>no<span class="Apple-tab-span" style="white-space:pre"> </span>eth1</div></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"><br></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"><div style="margin: 0px;">root@test:~# vconfig add vmbr1 10</div><div style="margin: 0px;">Added VLAN with VID == 10 to IF -:vmbr1:-</div><div style="margin: 0px;"><br></div><div style="margin: 0px;"><div style="margin: 0px;">root@test:~# ip link set vmbr1.10 up</div><div style="margin: 0px;"><br></div><div style="margin: 0px;"><div style="margin: 0px;">root@test:~# ifconfig</div><div style="margin: 0px;"><br></div></div></div></div><div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">vmbr1.10 Link encap:Ethernet HWaddr 86:60:41:ad:f4:0c </div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"> inet6 addr: fe80::8460:41ff:fead:f40c/64 Scope:Link</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"> RX packets:0 errors:0 dropped:0 overruns:0 frame:0</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"> collisions:0 txqueuelen:0 </div><div style="margin: 0px; font-size: 11px; font-family: Menlo;"> RX bytes:0 (0.0 B) TX bytes:328 (328.0 B)</div></div><div><br></div><div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">root@test:~# brctl addbr vmbr2</div></div><div><br></div><div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">root@test:~# brctl addif vmbr2 vmbr1.10</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">root@test:~# brctl show</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">bridge name<span class="Apple-tab-span" style="white-space:pre"> </span>bridge id<span class="Apple-tab-span" style="white-space:pre"> </span>STP enabled<span class="Apple-tab-span" style="white-space:pre"> </span>interfaces</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">vmbr1<span class="Apple-tab-span" style="white-space:pre"> </span>8000.866041adf40c<span class="Apple-tab-span" style="white-space:pre"> </span>no<span class="Apple-tab-span" style="white-space:pre"> </span>eth1</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;">vmbr2<span class="Apple-tab-span" style="white-space:pre"> </span>8000.866041adf40c<span class="Apple-tab-span" style="white-space:pre"> </span>no<span class="Apple-tab-span" style="white-space:pre"> </span>vmbr1.10</div></div><div><br></div></div><div style=" orphans: 2; widows: 2;"><br></div><div style=" orphans: 2; widows: 2;">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.</div></div><div style=" orphans: 2; widows: 2;"><br></div><div style=" orphans: 2; widows: 2;">Mixed tagging is not be possible with this patch, you can only choose for bridge tagging or normal interface tagging over the trigger.</div><div style=" orphans: 2; widows: 2;"><br></div><div style=" orphans: 2; widows: 2;">It’s time for VXLAN?</div><div style=" orphans: 2; widows: 2;"><br></div>
</div>
<br><div><div>Am 10.01.2014 um 14:23 schrieb Stefan Priebe - Profihost AG <<a href="mailto:s.priebe@profihost.ag">s.priebe@profihost.ag</a>>:</div><br class="Apple-interchange-newline"><blockquote type="cite">Yes and it also does not work with vlan starting with kernel 3.9 or 3.10.<br><br>Stefan<br><br>Am 10.01.2014 14:20, schrieb Alexandre DERUMIER:<br><blockquote type="cite">Hi,<br>If I remember Stefan Priebe use this kind of configuration and had send patchs last year.<br><br>But it was breaking some setup for me, with kernel 2.6.32.<br><br>I think this kind of config was broken (mixing tagging on eth and bridge)<br><br>eth0 -> eth0.tag -> bridge0 -> vm <br>eth0 -> bridge1 -> bridge1.tag -> bridge2 -> vm <br><br><br>----- Mail original ----- <br><br>De: "Johannes Ernst" <<a href="mailto:info@filemedia.de">info@filemedia.de</a>> <br>À: <a href="mailto:pve-devel@pve.proxmox.com">pve-devel@pve.proxmox.com</a> <br>Envoyé: Vendredi 10 Janvier 2014 14:17:33 <br>Objet: Re: [pve-devel] [PATCH] Virtual vlan tagging to bridge interface <br><br>Hello, <br><br><br>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. <br><br><br>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. <br><br><br><br>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. <br><br><br>For example: <br><br><br>1) normal solution <br><br><br>eth0 -> eth0.tag -> bridge1 -> vm <br><br><br>2) virtual tagged solution <br><br><br>eth0 -> bridge1 -> bridge1.tag -> bridge2 -> vm <br><br><br><br>Live print: <br><br><br><br>vmbr1 8000.666d7626577a no dummy0 <br>eth2 <br><br><br><br><br>vmbr1v1 8000.666d7626577a no tap113i1 <br>vmbr1.1 <br><br><br>It should be nice if everyone can test it too. <br><br><br><br><br><br><br>A short description for that patch would be helpful. <br><br><br><br>_______________________________________________ <br>pve-devel mailing list <br><a href="mailto:pve-devel@pve.proxmox.com">pve-devel@pve.proxmox.com</a> <br><a href="http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel">http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel</a> <br>_______________________________________________<br>pve-devel mailing list<br><a href="mailto:pve-devel@pve.proxmox.com">pve-devel@pve.proxmox.com</a><br>http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel<br><br></blockquote></blockquote></div><br></body></html>