[ovs-discuss] Is there a way to allow Promiscuous mode for a VM connected to vnetX on OVS?

Dmitri Chebotarov dchebota at gmu.edu
Fri Aug 30 15:50:36 UTC 2013


Hi

I'm looking for some help with an OVS option – is there a way to allow interface of connected VM to operate in promiscuous mode?
VMWare vSwitch has this under Security, VirtualBox under Network->[Adapter]->Advanced->Promiscuous mode.
It's in Deny by default – is a way to change it to Allow for specific VM port on OVS?

I'm trying to build a bridge between two locations/sites to extend my network to a different location (cloud).
The bridge is running inside VMs, VMs are hosted on KVM (RHEL6) /w OVS (v1.10).
I get broadcast traffic reaching to other sides on VM0, but in never leaves eth1 interface and VM on the same L2 network don't 'see' it.
I can confirm it with tcpdump.

I'M attaching a quick diagram – I hope it doesn't make it look more complicated that it's :)
All VM0/1/n are Ubuntu 12.04 guests running on KVM.

I'Ve duplicated the same setup on my local WKS using VirtualBox and all works as expected ONLY WHEN I allow promiscuous mode for the corresponding adapter for eth1 on VM0.

I cannot find a way to allow promiscuous mode for corresponding vent adapter on KVM/OVS (VM0:eth1).
Tried 'ifconfig vnetX promisc', but I don't think this is correct.

Thank you for the help.

--
Thank you,

Dmitri Chebotarov
VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & Messaging
223 Aquia Building, Ffx, MSN: 1B5
Phone: (703) 993-6175 | Fax: (703) 993-3404
[cid:D582E859-091B-4D75-9BEE-2304A90EC48F]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20130830/1bad03d8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2013-08-30 at 11.42.04 .png
Type: image/png
Size: 84631 bytes
Desc: Screen Shot 2013-08-30 at 11.42.04 .png
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20130830/1bad03d8/attachment-0002.png>


More information about the discuss mailing list