Re: [ovs-dev] Traffic Separation with OpenFlow

2012-07-11 Thread Justin Pettit
[Please keep this on the list.] I don't think you need to use queues. Just rules of the form: ovs-ofctl add-flow priority=100,in_port=1,tcp,tp_dst=5001,output=3 ovs-ofctl add-flow priroity=50,in_port=1,output=2 ovs-ofctl add-flow priroity=50,in_port=2,output=1

Re: [ovs-dev] Traffic Separation with OpenFlow

2012-07-11 Thread Justin Pettit
It should be pretty straight-forward with the "ovs-ofctl add-flow" command. There's a pretty extensive man page for the ovs-ofctl program. --Justin On Jul 11, 2012, at 3:19 PM, Anand Daga wrote: > System: > We have a VM 10.70.11.86 on a XENServer with OVS. The VM is connected to the > OVS(xe

[ovs-dev] Traffic Separation with OpenFlow

2012-07-11 Thread Anand Daga
*System:* We have a VM 10.70.11.86 on a XENServer with OVS. The VM is connected to the OVS(xenbr0) on tap1.0 which is port 1 of OVS. Now we have 2 physical n/w interfaces namely eth0 & eth1 on OVS port 2 & 3 resp. *System diagram:* <> ---> tap1.0 <>