Hi Ben Could you please let me know if this feature implementation is supported in OVS or not.
Also, I am new to this and do not know how I can find status of EXT-406. Meanwhile I found this below link online which gives a way to implement this flag it is by changing fm->flags=2; in ofp-parse.c http://openvswitch.org/pipermail/discuss/2012-January/006406.html I tried this and it does not work. Thanks & Regards Sandhya On Tue, Dec 2, 2014 at 11:34 AM, Ben Pfaff <b...@nicira.com> wrote: > On Tue, Dec 02, 2014 at 11:30:26AM -0800, Ben Pfaff wrote: > > On Mon, Dec 01, 2014 at 10:50:45PM -0800, varanasi sandhya wrote: > > > OFPFF_CHECK_OVERLAP flag Issue: > > > > > > When OFPFF_CHECK_OVERLAP flag is set at RYU controller in ofctl_v1_3.py > > > code in the mod_flow_entry definition, OVS should ideally return > > > OFPFMFC_OVERLAP error on inserting a duplicate flow with same priority > and > > > match. But instead the new flow entry just replaces the old flow. > > > > Do you have evidence to support this interpretation of the OpenFlow > > specification? > > In fact, this is an unresolved question in the OpenFlow specification > working group. Open issue EXT-406 addresses it. I just added a > comment to try to revive the issue. > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
