Re: [ovirt-users] Passing VLAN trunk to VM

Hi Everyone, I try to use as we talk about not define a vlan tag, but does not work. I try using tag vlan and bond + tag vlan. Seems as you can see, ovirt attach vlan id 0 ( reserved to untagged vlan on a trunck - http://standards.ieee.org/getieee802/download/802.1Q-2005.pdf ). [image: pasted3] [image: pasted4] [image: pasted5] [image: pasted2][image: pasted1] Em dom, 12 de mar de 2017 às 11:33, Edward Haas <ehaas(a)redhat.com&gt; escreveu: > On Sun, Mar 12, 2017 at 3:43 PM, Rogério Ceni Coelho < > rogeriocenicoelho(a)gmail.com&gt; wrote: > > I think you define vlans on vm virtual nic OS like you do as usual. > Monday i will try and share results. Bye. > > Em Dom, 12 de mar de 2017 10:40, FERNANDO FREDIANI < > fernando.frediani(a)upx.com&gt; escreveu: > > Great ! > > What about a range of VLANs, is it also supported ? > > > That was the OVS note all about, only with an OVS bridge it is possible > to define/select the vlans which are exposed > to the VM vnic. But this is not available at the moment. > As Rogério mentioned, define the VLAN/s on the VM vnic. > > > 2017-03-11 17:47 GMT-03:00 Edward Haas <ehaas(a)redhat.com&gt;: > > Passing a trunk to the vnic is supported long ago. > Just create a network over a nic/bond that is connected to a trunk port > and do not define any VLAN (we call it non vlan network). > In oVirt, a non-vlan network will ignore the VLAN tag and will forward > the packets as is onward. > It is up to the VM vnic to define vlans or use a promisc mode to see > everything. > > OVS can add a layer of security over the existing, by defining explicitly > which vlans are allowed for a specific vnic, but it is not > currently available. > > > On Thu, Mar 9, 2017 at 11:40 PM, Simon Vincent <sv(a)srvincent.co.uk&gt; > wrote: > > I was wondering if open vswitch will get round this problem. Has anyone > tried it? > > On 9 Mar 2017 7:41 pm, "Rogério Ceni Coelho" <rogeriocenicoelho(a)gmail.com&gt; > wrote: > > Hi, > > Ovirt user interface does not allow to input 4095 as a tag vlan number > ... Only values between 0 and 4094. > > This is useful to me too. Maybe any other way ? > > Em qui, 9 de mar de 2017 às 16:15, FERNANDO FREDIANI < > fernando.frediani(a)upx.com&gt; escreveu: > > Have you tried use Vlan 4095 ? On VMware it used to be the way to pass > all Vlans from a vSwitch to a Vlan in a single port. And yes I have used it > also for pfSense. > > Fernando > > On 09/03/2017 16:09, Simon Vincent wrote: > > Is it possible to pass multiple VLANs to a VM (pfSense) using a single > virtual NIC? All my existing oVirt networks are setup as a single tagged > VLAN. I know this didn't used to be supported but wondered if this has > changed. My other option is to pass each VLAN as a separate NIC to the VM > however if I needed to add a new VLAN I would have to add a new interface > and reboot the VM as hot-add of NICs is not supported by pfSense. > > > > > _______________________________________________ > Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > >