[Please keep this on the list.]
I don't think you need to use queues. Just rules of the form:
ovs-ofctl add-flow <br> priority=100,in_port=1,tcp,tp_dst=5001,output=3
ovs-ofctl add-flow <br> priroity=50,in_port=1,output=2
ovs-ofctl add-flow <br> priroity=50,in_port=2,output=1
ovs-ofctl add-flow <br> priority=50,in_port=3,output=1
These weren't tested, but it should at least be enough to get you pointed in
the right direction
--Justin
On Jul 11, 2012, at 3:28 PM, Anand Daga wrote:
> Hello Justin,
>
> Can you please point me to some examples? I'm able to add flow that uses
> different queues on 1 port but sending them on different ports seems to be a
> problem.
>
> Thanks,
> Anand
>
> On Wed, Jul 11, 2012 at 3:25 PM, Justin Pettit <jpet...@nicira.com> wrote:
> 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(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:
> > <<VM 10.70.11.86 VM>> ---> tap1.0 <<OVS port 1=tap1.0, >>
> > << port 2=eth0,
> > >>---->outside
> > << port 3=eth1
> > >>---->outside
> >
> >
> > Problem:
> > How to direct traffic coming from VM's port 5001 to only eth1. All the
> > other traffic should go to eth0. What flows should we insert to achieve
> > this?
> > Desired traffic separation: from port 5001 ---> to eth1
> > all traffic except from 5001 -->
> > to eth0
> >
> > Thanks,
> > Anand
> > _______________________________________________
> > dev mailing list
> > dev@openvswitch.org
> > http://openvswitch.org/mailman/listinfo/dev
>
>
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
