[ovs-dev] Forwarding packet to multiple switch ports

[hardik soni]

Thanks Ben for the answer, I should have read the FAQ before posting.
Now, I need to check what Mininet is doing while setting up the topology
for simulations.

Thanks for the multiple quick responses. I appreciate it.


On 7 January 2014 19:33, Ben Pfaff <blp at nicira.com> wrote:

> On Tue, Jan 07, 2014 at 07:20:58PM +0100, hardik soni wrote:
> > what is the highest version of openflow implemented in 2.0.0 ovs?
> > And how to enable it?
>
> Please read the FAQ.
>
> Q: What versions of OpenFlow does Open vSwitch support?
>
> A: Open vSwitch 1.9 and earlier support only OpenFlow 1.0 (plus
>    extensions that bring in many of the features from later versions
>    of OpenFlow).
>
>    Open vSwitch 1.10 and later have experimental support for OpenFlow
>    1.2 and 1.3.  On these versions of Open vSwitch, the following
>    command enables OpenFlow 1.0, 1.2, and 1.3 on bridge br0:
>
>        ovs-vsctl set bridge br0 protocols=OpenFlow10,OpenFlow12,OpenFlow13
>
>    Open vSwitch version 2.0 and later will have experimental support
>    for OpenFlow 1.1, 1.2, and 1.3.  On these versions of Open vSwitch,
>    the following command enables OpenFlow 1.0, 1.1, 1.2, and 1.3 on
>    bridge br0:
>
>        ovs-vsctl set bridge br0
> protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13
>
>    Use the -O option to enable support for later versions of OpenFlow
>    in ovs-ofctl.  For example:
>
>        ovs-ofctl -O OpenFlow13 dump-flows br0
>
>    Support for OpenFlow 1.1, 1.2, and 1.3 is still incomplete.  Work
>    to be done is tracked in OPENFLOW-1.1+ in the Open vSwitch sources
>    (also via http://openvswitch.org/development/openflow-1-x-plan/).
>    When support for a given OpenFlow version is solidly implemented,
>    Open vSwitch will enable that version by default.
>



-- 
Regards,
Hardik Soni
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-dev/attachments/20140107/46d84892/attachment-0003.html>