As Ben notes, the simplest option for anyone who wants OpenFlow 1.3 on OVS is
to upgrade to OVS 2.3.
(If you are using Mininet, it even provides a shortcut: mininet/util/install.sh
-V 2.3)
As he also implies, another option is to have Mininet enable it explicitly, e.g.
mn --switch ovs,protocols=OpenFlow13
(follow-up to mininet-discuss)
> On Jan 20, 2015, at 7:25 AM, Ben Pfaff <[email protected]> wrote:
>
> Please don't drop the mailing list.
>
> On Tue, Jan 20, 2015 at 04:21:50PM +0100, Kevin Neuenfeldt wrote:
>> Am 20.01.2015 um 15:37 schrieb Ben Pfaff:
>>> On Tue, Jan 20, 2015 at 03:07:43PM +0100, Kevin Neuenfeldt wrote:
>>>> So is there any possibility to enable OpenFlow 1.3 globally and
>>>> permanently?
>>>
>>> I guess that mininet uses ovs-vsctl to create the bridges. I would just
>>> change mininet to enable OpenFlow 1.3 at the same time it creates the
>>> bridges, by executing another ovs-vsctl command.
>>>
>> This would be a possibility but because I will have to collaborate with
>> students from other universities it's preferable to not change mininet
>> itself.
>
> You can change openvswitch or you can change mininet. I can't think why
> either choice would make collaboration more difficult.
>
> The simplest choice is to use OVS 2.3, which enables OF1.3 by default.
> _______________________________________________
> discuss mailing list
> [email protected]
> http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
